Project Number Date
test_Tails_ISO_stable 4919 08 Jul 2024, 15:46

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 19:35.532 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:22.058
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.903
When I start Tails from USB drive "old" with network unplugged 1:44.809
Then the boot device has safe access rights 3.050
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.780
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.768
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:26.493
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.758
And I take note of which tps features are available 1.604
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 6.586
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.662
Before features/support/hooks.rb:269 0.008
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.549
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.081
When I write some files expected to persist 1.769
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.544
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.432
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.291
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.843
And I log in to a new session 17.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.586
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.697
Then the running Tails is installed on USB drive "to_upgrade" 17.163
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 4.366
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.323
Before features/support/hooks.rb:269 0.009
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.126
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.178
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.358
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:32.636
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 11.273
And no SquashFS delta is installed 0.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.030
And Tor is ready 17.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.852
Given I shutdown Tails and wait for the computer to power off 9.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.347
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.426
And only the 6.2~testoverlayfs SquashFS delta is installed 0.127
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.318
When the network is plugged 0.039
And Tor is ready 21.407
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.849
Given I shutdown Tails and wait for the computer to power off 4.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.458
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.897
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.039
And Tor is ready 19.139
Then the Upgrader considers the system as up-to-date 0.331
# 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.303
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
54.790
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.742
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 42.784
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.697
After features/support/hooks.rb:326 0.905
After features/support/hooks.rb:100 0.000