Project Number Date
test_Tails_ISO_stable 4799 19 Apr 2024, 12:10

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 18:40.651 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
1:55.976
Before features/support/hooks.rb:259 0.008
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 24.500
When I start Tails from USB drive "old" with network unplugged 1:26.205
Then the boot device has safe access rights 3.042
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:305 3.504
After features/support/hooks.rb:89 0.010
Tags: @product
2:4.687
Before features/support/hooks.rb:259 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:19.628
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 34.042
And I take note of which tps features are available 1.197
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.478
After features/support/hooks.rb:305 0.184
After features/support/hooks.rb:89 0.008
Tags: @product
2:46.158
Before features/support/hooks.rb:259 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.692
Then Tails is running from USB drive "old" 0.315
And all tps features are active 2.134
When I write some files expected to persist 1.849
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 2.827
And I take note of which tps features are available 0.653
And I shutdown Tails and wait for the computer to power off 4.238
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.519
After features/support/hooks.rb:305 0.123
After features/support/hooks.rb:89 0.011
Tags: @product
2:33.065
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.106
And I log in to a new session 21.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.605
And I plug USB drive "to_upgrade" 2.629
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.927
Then the running Tails is installed on USB drive "to_upgrade" 19.027
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.112
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.432
Before features/support/hooks.rb:259 0.007
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.428
Then all tps features from the old Tails version are active 1.744
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.633
And all persistent directories from the old Tails version have safe access rights 2.609
After features/support/hooks.rb:305 0.659
After features/support/hooks.rb:89 0.010
6:27.694
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.572
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.042
And Tor is ready 20.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.803
Given I shutdown Tails and wait for the computer to power off 6.778
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.966
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.355
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.057
And Tor is ready 17.608
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.968
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.042
Given I shutdown Tails and wait for the computer to power off 4.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.215
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.040
And Tor is ready 15.807
Then the Upgrader considers the system as up-to-date 0.280
# 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 15.011
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.915
After features/support/hooks.rb:305 0.746
After features/support/hooks.rb:89 0.021
37.637
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.732
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 19.529
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.714
After features/support/hooks.rb:305 0.638
After features/support/hooks.rb:89 0.000