Project Number Date
test_Tails_ISO_stable 5577 15 Apr 2025, 23:25

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:8.252 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.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.160
When I start Tails from USB drive "old" with network unplugged 1:26.954
Then the boot device has safe access rights 2.979
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 1.092
After features/support/hooks.rb:100 0.007
Tags: @product
2:6.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:25.472
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 28.574
And I take note of which tps features are available 2.449
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.326
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.669
Then Tails is running from USB drive "old" 0.351
And all tps features are active 1.973
When I write some files expected to persist 1.875
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.392
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.359
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.354
And I log in to a new session 18.295
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.090
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.802
Then the running Tails is installed on USB drive "to_upgrade" 23.028
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 1.143
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.352
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.382
After features/support/hooks.rb:330 1.457
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:36.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.057
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.755
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.065
And Tor is ready 22.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.809
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.594
Given I shutdown Tails and wait for the computer to power off 8.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.724
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.280
When the network is plugged 0.073
And Tor is ready 21.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.519
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.626
Given I shutdown Tails and wait for the computer to power off 4.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.742
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.054
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.065
And Tor is ready 17.437
Then the Upgrader considers the system as up-to-date 0.336
# 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.985
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.605
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.029
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.800
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 21.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.901
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.000