Project Number Date
test_Tails_ISO_stable 5075 05 Sep 2024, 18:46

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:14.515 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:4.989
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
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.063
When I start Tails from USB drive "old" with network unplugged 1:27.367
Then the boot device has safe access rights 3.196
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.679
Before features/support/hooks.rb:269 0.008
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:23.240
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.919
And I take note of which tps features are available 2.378
Then a Tails persistence partition exists on USB drive "old" 1.196
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.986
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.580
Then Tails is running from USB drive "old" 0.342
And all tps features are active 2.016
When I write some files expected to persist 1.886
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.530
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.744
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.687
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.013
Tags: @product
2:26.896
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 11.788
And I log in to a new session 18.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.150
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.007
Then the running Tails is installed on USB drive "to_upgrade" 17.226
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 3.321
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.190
Before features/support/hooks.rb:269 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.080
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.902
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:43.851
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.885
And no SquashFS delta is installed 0.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.077
And Tor is ready 20.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.967
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.248
Given I shutdown Tails and wait for the computer to power off 15.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.398
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.151
And the file system changes introduced in version 6.2~testoverlayfs are present 0.473
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.417
# 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.075
And Tor is ready 18.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.640
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.608
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.023
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.084
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.071
And Tor is ready 18.227
Then the Upgrader considers the system as up-to-date 0.355
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.036
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
35.921
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 1.255
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.281
After features/support/hooks.rb:326 1.264
After features/support/hooks.rb:100 0.000