Project Number Date
test_Tails_ISO_stable 4728 19 Mar 2024, 18:05

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:56.228 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.568
Before features/support/hooks.rb:245 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 19.792
When I start Tails from USB drive "old" with network unplugged 1:35.617
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:291 7.505
After features/support/hooks.rb:75 0.008
Tags: @product
2:0.011
Before features/support/hooks.rb:245 0.004
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:15.669
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 33.402
And I take note of which tps features are available 1.533
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 8.103
After features/support/hooks.rb:291 0.170
After features/support/hooks.rb:75 0.011
Tags: @product
2:40.558
Before features/support/hooks.rb:245 0.009
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.611
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.027
When I write some files expected to persist 1.605
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 3.473
And I take note of which tps features are available 0.748
And I shutdown Tails and wait for the computer to power off 4.025
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.859
After features/support/hooks.rb:291 0.155
After features/support/hooks.rb:75 0.009
Tags: @product
2:26.467
Before features/support/hooks.rb:245 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 12.227
And I log in to a new session 17.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.397
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.149
Then the running Tails is installed on USB drive "to_upgrade" 15.406
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:291 6.867
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.027
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.398
Then all tps features from the old Tails version are active 1.510
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.630
And all persistent directories from the old Tails version have safe access rights 2.654
After features/support/hooks.rb:291 0.864
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:7.790
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.258
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.033
And Tor is ready 19.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.535
Given I shutdown Tails and wait for the computer to power off 6.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.846
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.950
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.227
When the network is plugged 0.050
And Tor is ready 20.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.181
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.567
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.333
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.831
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.043
And Tor is ready 18.011
Then the Upgrader considers the system as up-to-date 0.232
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.921
After features/support/hooks.rb:291 0.723
After features/support/hooks.rb:75 0.015
Tags: @product @automatic_upgrade
34.805
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.446
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.672
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 18.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.355
After features/support/hooks.rb:291 0.774
After features/support/hooks.rb:75 0.000