Project Number Date
test_Tails_ISO_stable 5539 31 Mar 2025, 13:10

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:18.074 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:14.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.256
And I create a 7200 MiB disk named "old" 0.518
And I plug USB drive "old" 1.280
And I write an old version of the Tails USB image to disk "old" 32.795
When I start Tails from USB drive "old" with network unplugged 1:34.620
Then the boot device has safe access rights 3.405
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.284
After features/support/hooks.rb:330 7.181
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:36.482
Then Tails is running from USB drive "old" 0.433
And I create a persistent partition 32.446
And I take note of which tps features are available 2.060
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 9.008
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.463
Then Tails is running from USB drive "old" 1.069
And all tps features are active 2.284
When I write some files expected to persist 2.735
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.822
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 6.866
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.115
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.432
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 11.303
And I log in to a new session 21.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.525
Then the running Tails is installed on USB drive "to_upgrade" 27.503
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 1.050
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.771
Then all tps features from the old Tails version are active 1.923
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.817
After features/support/hooks.rb:330 1.560
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.344
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.423
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.142
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.461
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.091
And Tor is ready 22.392
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.193
Given I shutdown Tails and wait for the computer to power off 10.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.196
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.515
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
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.388
# 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.277
When the network is plugged 0.068
And Tor is ready 18.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.026
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.341
Given I shutdown Tails and wait for the computer to power off 4.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.512
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.218
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.080
And Tor is ready 20.268
Then the Upgrader considers the system as up-to-date 0.370
# 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 16.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.641
After features/support/hooks.rb:330 0.854
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.180
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 9.637
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.637
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.144
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 18.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.685
After features/support/hooks.rb:330 0.811
After features/support/hooks.rb:100 0.000