Project Number Date
test_Tails_ISO_devel 3750 23 Mar 2025, 13:19

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:30.485 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:21.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.213
When I start Tails from USB drive "old" with network unplugged 1:45.114
Then the boot device has safe access rights 2.960
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.736
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:25.243
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 32.691
And I take note of which tps features are available 1.870
Then a Tails persistence partition exists on USB drive "old" 1.007
And I shutdown Tails and wait for the computer to power off 8.688
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.128
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.059
Then Tails is running from USB drive "old" 0.833
And all tps features are active 2.138
When I write some files expected to persist 2.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.661
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.395
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.438
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.640
And I log in to a new session 19.314
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.994
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.082
Then the running Tails is installed on USB drive "to_upgrade" 25.474
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 2.227
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.156
Then all tps features from the old Tails version are active 1.898
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.922
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 3.351
After features/support/hooks.rb:330 1.727
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:32.300
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.611
And no SquashFS delta is installed 0.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.568
When the network is plugged 0.066
And Tor is ready 19.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.033
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.028
Given I shutdown Tails and wait for the computer to power off 8.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.059
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
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.385
# 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.439
When the network is plugged 0.124
And Tor is ready 20.521
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.938
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.803
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.213
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.656
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.534
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.904
When the network is plugged 0.080
And Tor is ready 16.763
Then the Upgrader considers the system as up-to-date 0.310
# 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.034
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.011
After features/support/hooks.rb:330 0.753
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.552
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.674
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.695
After features/support/hooks.rb:330 1.027
After features/support/hooks.rb:100 0.000