Project Number Date
test_Tails_ISO_stable 5306 30 Nov 2024, 13:11

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 20:3.501 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:29.565
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.470
When I start Tails from USB drive "old" with network unplugged 1:51.452
Then the boot device has safe access rights 3.284
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.447
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.719
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:33.906
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 33.476
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.736
And I shutdown Tails and wait for the computer to power off 8.618
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.734
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.368
Then Tails is running from USB drive "old" 0.550
And all tps features are active 2.062
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 3.264
And I take note of which tps features are available 0.971
And I shutdown Tails and wait for the computer to power off 4.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.494
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.618
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.109
And I log in to a new session 20.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.820
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.747
Then the running Tails is installed on USB drive "to_upgrade" 22.055
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:326 2.666
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.606
Before features/support/hooks.rb:269 0.007
Given a computer 0.480
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.237
Then all tps features from the old Tails version are active 1.957
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.213
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.790
After features/support/hooks.rb:326 0.928
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:40.956
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.891
And no SquashFS delta is installed 0.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.096
And Tor is ready 21.999
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.374
Given I shutdown Tails and wait for the computer to power off 13.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.479
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.339
When the network is plugged 0.067
And Tor is ready 18.307
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.400
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.326
Given I shutdown Tails and wait for the computer to power off 4.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.104
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.065
And Tor is ready 18.683
Then the Upgrader considers the system as up-to-date 0.331
# 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 15.413
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.118
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.299
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.612
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 1.168
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.308
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.000