Project Number Date
test_Tails_ISO_devel 3789 28 Apr 2025, 13:13

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 20:59.170 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:32.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.435
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.086
And I write an old version of the Tails USB image to disk "old" 39.861
When I start Tails from USB drive "old" with network unplugged 1:46.053
Then the boot device has safe access rights 3.473
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.260
After features/support/hooks.rb:330 3.775
After features/support/hooks.rb:100 0.013
Tags: @product
2:15.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:29.893
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.653
And I take note of which tps features are available 2.503
Then a Tails persistence partition exists on USB drive "old" 0.917
And I shutdown Tails and wait for the computer to power off 9.248
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.774
Then Tails is running from USB drive "old" 0.494
And all tps features are active 2.491
When I write some files expected to persist 2.064
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.797
And I take note of which tps features are available 0.570
And I shutdown Tails and wait for the computer to power off 4.524
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.091
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.927
And I log in to a new session 24.535
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.813
And I plug USB drive "to_upgrade" 2.549
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.954
Then the running Tails is installed on USB drive "to_upgrade" 25.250
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:330 1.632
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.135
Then all tps features from the old Tails version are active 2.680
And Tails is running from USB drive "to_upgrade" 0.409
And the boot device has safe access rights 3.959
And the expected persistent files created with the old Tails version are present in the filesystem 1.743
And all persistent directories from the old Tails version have safe access rights 2.915
After features/support/hooks.rb:330 1.481
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:15.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.945
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.151
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.113
And Tor is ready 22.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.433
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.123
Given I shutdown Tails and wait for the computer to power off 9.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.959
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.800
And the file system changes introduced in version 6.2~testoverlayfs are present 0.471
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.125
And Tor is ready 21.544
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.126
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.456
Given I shutdown Tails and wait for the computer to power off 4.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.649
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.110
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.387
When the network is plugged 0.078
And Tor is ready 20.628
Then the Upgrader considers the system as up-to-date 0.392
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 17.479
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.822
After features/support/hooks.rb:330 0.800
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
40.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.659
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the signing key used by the Upgrader is outdated 0.282
But a current signing key is available on our website 0.000
When the network is plugged 0.123
And Tor is ready 22.204
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.316
After features/support/hooks.rb:330 1.966
After features/support/hooks.rb:100 0.000