Project Number Date
test_Tails_ISO_stable 4747 27 Mar 2024, 12:14

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:40.358 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:40.885
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 21.029
When I start Tails from USB drive "old" with network unplugged 1:14.612
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:291 3.525
After features/support/hooks.rb:75 0.025
Tags: @product
2:6.459
Before features/support/hooks.rb:245 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:19.072
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.817
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 10.689
After features/support/hooks.rb:291 0.185
After features/support/hooks.rb:75 0.008
Tags: @product
2:41.403
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.787
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.952
When I write some files expected to persist 2.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.767
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.398
After features/support/hooks.rb:291 0.142
After features/support/hooks.rb:75 0.011
Tags: @product
2:20.134
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.216
And I log in to a new session 17.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.465
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.519
Then the running Tails is installed on USB drive "to_upgrade" 12.764
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 4.189
After features/support/hooks.rb:75 0.000
Tags: @product
2:13.043
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.147
Then all tps features from the old Tails version are active 1.498
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.990
And the expected persistent files created with the old Tails version are present in the filesystem 1.620
And all persistent directories from the old Tails version have safe access rights 2.308
After features/support/hooks.rb:291 0.703
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:6.164
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.768
And no SquashFS delta is installed 0.078
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.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.041
And Tor is ready 18.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.839
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.019
Given I shutdown Tails and wait for the computer to power off 6.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.034
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.873
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.269
When the network is plugged 0.059
And Tor is ready 18.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.820
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.640
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.912
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.031
And Tor is ready 16.311
Then the Upgrader considers the system as up-to-date 10.624
# 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.185
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.863
After features/support/hooks.rb:291 0.763
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
32.267
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.785
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.046
And the signing key used by the Upgrader is outdated 1.060
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 14.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.483
After features/support/hooks.rb:291 0.807
After features/support/hooks.rb:75 0.000