Project Number Date
test_Tails_ISO_stable 5034 18 Aug 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:19.900 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:0.012
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.435
When I start Tails from USB drive "old" with network unplugged 1:25.412
Then the boot device has safe access rights 2.928
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.722
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.841
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:20.229
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 31.652
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.237
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.620
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.668
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.753
When I write some files expected to persist 1.948
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.259
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 4.278
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.237
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.950
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.157
And I log in to a new session 18.791
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.879
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.676
Then the running Tails is installed on USB drive "to_upgrade" 17.649
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 3.075
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.676
Before features/support/hooks.rb:269 0.007
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.943
Then all tps features from the old Tails version are active 1.415
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.136
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.715
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.892
And no SquashFS delta is installed 0.177
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
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.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.091
And Tor is ready 21.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.622
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.841
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.336
When the network is plugged 0.071
And Tor is ready 19.309
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.916
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.621
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.520
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.351
When the network is plugged 0.064
And Tor is ready 18.813
Then the Upgrader considers the system as up-to-date 0.304
# 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 13.436
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.922
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.083
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.007
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.734
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 19.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.987
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.000