Project Number Date
test_Tails_ISO_stable 5056 29 Aug 2024, 08:49

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 21:1.089 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:31.381
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.085
And I write an old version of the Tails USB image to disk "old" 33.551
When I start Tails from USB drive "old" with network unplugged 1:52.379
Then the boot device has safe access rights 3.038
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.333
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:26.809
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 32.264
And I take note of which tps features are available 2.155
Then a Tails persistence partition exists on USB drive "old" 0.931
And I shutdown Tails and wait for the computer to power off 8.572
After features/support/hooks.rb:326 0.211
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.753
Before features/support/hooks.rb:269 0.021
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.807
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.214
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 3.128
And I take note of which tps features are available 0.542
And I shutdown Tails and wait for the computer to power off 4.583
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.392
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.926
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.376
And I log in to a new session 23.884
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.295
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.796
Then the running Tails is installed on USB drive "to_upgrade" 21.695
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 3.079
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.609
Before features/support/hooks.rb:269 0.007
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.028
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.872
And the expected persistent files created with the old Tails version are present in the filesystem 1.613
And all persistent directories from the old Tails version have safe access rights 2.713
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:42.614
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.708
And no SquashFS delta is installed 0.199
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.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.079
And Tor is ready 19.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.871
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.881
Given I shutdown Tails and wait for the computer to power off 11.166
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.309
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.400
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.278
When the network is plugged 0.078
And Tor is ready 18.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.287
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.513
Given I shutdown Tails and wait for the computer to power off 4.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.937
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.289
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.085
And Tor is ready 18.611
Then the Upgrader considers the system as up-to-date 10.881
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
36.469
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.098
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.600
After features/support/hooks.rb:326 0.804
After features/support/hooks.rb:100 0.000