Project Number Date
test_Tails_ISO_stable 5669 22 May 2025, 08:54

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:36.196 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:22.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 30.618
When I start Tails from USB drive "old" with network unplugged 1:46.755
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 6.829
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:23.027
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.942
And I take note of which tps features are available 1.959
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.336
After features/support/hooks.rb:330 0.394
After features/support/hooks.rb:100 0.042
Tags: @product
3:2.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.053
Given a computer 0.344
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.999
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.169
When I write some files expected to persist 1.986
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 6.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.505
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.015
Tags: @product
2:37.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.101
And I log in to a new session 20.567
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.603
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.071
Then the running Tails is installed on USB drive "to_upgrade" 27.011
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.146
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.957
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.349
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.443
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:330 1.340
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:36.743
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 with a persistent partition enabled and logged in 11.687
And no SquashFS delta is installed 0.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.866
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.062
And Tor is ready 21.586
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.192
Given I shutdown Tails and wait for the computer to power off 8.495
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.048
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.278
When the network is plugged 0.085
And Tor is ready 17.833
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.060
Given I shutdown Tails and wait for the computer to power off 4.193
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.187
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.023
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.080
And Tor is ready 21.400
Then the Upgrader considers the system as up-to-date 0.334
# 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.343
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.710
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.143
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 with a persistent partition enabled and logged in 10.529
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 21.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.007
After features/support/hooks.rb:330 0.885
After features/support/hooks.rb:100 0.000