Project Number Date
test_Tails_ISO_stable 4773 05 Apr 2024, 11:58

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 17:19.171 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:42.102
Before features/support/hooks.rb:259 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 22.765
When I start Tails from USB drive "old" with network unplugged 1:14.044
Then the boot device has safe access rights 3.004
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:305 7.346
After features/support/hooks.rb:89 0.015
Tags: @product
2:2.606
Before features/support/hooks.rb:259 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:16.107
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 35.186
And I take note of which tps features are available 1.468
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.448
After features/support/hooks.rb:305 0.170
After features/support/hooks.rb:89 0.009
Tags: @product
2:33.450
Before features/support/hooks.rb:259 0.005
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.553
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.966
When I write some files expected to persist 1.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.505
And all persistent directories from the old Tails version have safe access rights 2.575
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 4.117
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.463
After features/support/hooks.rb:305 0.191
After features/support/hooks.rb:89 0.018
Tags: @product
2:27.542
Before features/support/hooks.rb:259 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.366
And I log in to a new session 17.333
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.375
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.369
Then the running Tails is installed on USB drive "to_upgrade" 17.304
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:305 2.426
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.600
Before features/support/hooks.rb:259 0.006
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.311
Then all tps features from the old Tails version are active 1.871
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.062
And the expected persistent files created with the old Tails version are present in the filesystem 1.390
And all persistent directories from the old Tails version have safe access rights 2.434
After features/support/hooks.rb:305 1.351
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:1.451
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.382
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.058
And Tor is ready 21.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.324
Given I shutdown Tails and wait for the computer to power off 6.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.626
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.082
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.320
When the network is plugged 0.031
And Tor is ready 17.109
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.035
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.172
Given I shutdown Tails and wait for the computer to power off 4.363
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.337
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.039
And Tor is ready 18.861
Then the Upgrader considers the system as up-to-date 0.240
# 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.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.919
After features/support/hooks.rb:305 0.719
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
32.417
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.494
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 16.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.561
After features/support/hooks.rb:305 0.774
After features/support/hooks.rb:89 0.000