Project Number Date
test_Tails_ISO_stable 4956 19 Jul 2024, 08:32

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:42.457 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:25.558
Before features/support/hooks.rb:269 0.004
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.085
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 45.530
When I start Tails from USB drive "old" with network unplugged 1:34.301
Then the boot device has safe access rights 3.253
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:326 3.565
After features/support/hooks.rb:100 0.019
Tags: @product
2:15.053
Before features/support/hooks.rb:269 0.006
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:30.527
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 32.108
And I take note of which tps features are available 2.039
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.836
After features/support/hooks.rb:326 0.238
After features/support/hooks.rb:100 0.015
Tags: @product
2:55.575
Before features/support/hooks.rb:269 0.004
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.755
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.426
When I write some files expected to persist 1.722
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.983
And I take note of which tps features are available 0.598
And I shutdown Tails and wait for the computer to power off 4.274
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.498
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.779
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 25.168
And I log in to a new session 19.146
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.432
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.034
Then the running Tails is installed on USB drive "to_upgrade" 21.116
And I unplug USB drive "to_upgrade" 0.262
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 7.667
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.999
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.293
Then all tps features from the old Tails version are active 1.610
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:326 0.903
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:20.282
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.560
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.035
And Tor is ready 20.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.330
Given I shutdown Tails and wait for the computer to power off 9.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.093
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.047
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.315
When the network is plugged 0.041
And Tor is ready 19.127
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.474
Given I shutdown Tails and wait for the computer to power off 6.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.220
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
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.454
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.049
And Tor is ready 19.187
Then the Upgrader considers the system as up-to-date 0.329
# 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 14.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.273
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
36.207
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
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 1.047
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 18.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.706
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000