Project Number Date
test_Tails_ISO_stable 5667 21 May 2025, 12:40

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:3.695 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:54.091
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.303
When I start Tails from USB drive "old" with network unplugged 1:18.329
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 0.969
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:23.329
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.114
And I take note of which tps features are available 1.661
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.715
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.006
When I write some files expected to persist 1.655
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.515
And all persistent directories from the old Tails version have safe access rights 3.807
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.880
After features/support/hooks.rb:330 0.100
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.447
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.211
And I log in to a new session 18.034
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.990
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.264
Then the running Tails is installed on USB drive "to_upgrade" 24.102
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:330 2.159
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.679
Then all tps features from the old Tails version are active 1.495
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.336
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.244
After features/support/hooks.rb:330 1.656
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.237
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 11.073
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.505
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.073
And Tor is ready 21.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.417
Given I shutdown Tails and wait for the computer to power off 8.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.926
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.953
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# 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.342
When the network is plugged 0.069
And Tor is ready 18.244
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.917
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.573
Given I shutdown Tails and wait for the computer to power off 6.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.980
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.078
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.060
And Tor is ready 20.029
Then the Upgrader considers the system as up-to-date 0.325
# 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.503
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.640
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
34.379
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.697
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.648
After features/support/hooks.rb:330 1.241
After features/support/hooks.rb:100 0.000