Project Number Date
test_Tails_ISO_devel 3808 13 May 2025, 13:18

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 21:7.653 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:36.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 32.928
When I start Tails from USB drive "old" with network unplugged 1:57.541
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.129
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.264
After features/support/hooks.rb:330 4.072
After features/support/hooks.rb:100 0.038
Tags: @product
2:25.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:34.158
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 37.628
And I take note of which tps features are available 2.576
Then a Tails persistence partition exists on USB drive "old" 1.317
And I shutdown Tails and wait for the computer to power off 9.003
After features/support/hooks.rb:330 0.255
After features/support/hooks.rb:100 0.012
Tags: @product
3:6.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.079
Then Tails is running from USB drive "old" 0.464
And all tps features are active 2.852
When I write some files expected to persist 1.916
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.612
And all persistent directories from the old Tails version have safe access rights 4.028
And I take note of which tps features are available 3.105
And I shutdown Tails and wait for the computer to power off 6.557
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.341
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.549
And I log in to a new session 24.644
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.026
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.775
Then the running Tails is installed on USB drive "to_upgrade" 29.741
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 2.262
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.476
Then all tps features from the old Tails version are active 1.940
And Tails is running from USB drive "to_upgrade" 0.445
And the boot device has safe access rights 3.470
And the expected persistent files created with the old Tails version are present in the filesystem 1.553
And all persistent directories from the old Tails version have safe access rights 2.623
After features/support/hooks.rb:330 1.137
After features/support/hooks.rb:100 0.010
7:1.776
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 21.093
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.164
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.471
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.068
And Tor is ready 23.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.295
Given I shutdown Tails and wait for the computer to power off 9.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.792
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.488
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.389
# 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.309
When the network is plugged 0.079
And Tor is ready 18.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.867
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.761
Given I shutdown Tails and wait for the computer to power off 6.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.468
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.079
And Tor is ready 20.127
Then the Upgrader considers the system as up-to-date 0.392
# 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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.633
After features/support/hooks.rb:330 0.776
After features/support/hooks.rb:100 0.020
41.540
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.556
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.256
After features/support/hooks.rb:330 1.274
After features/support/hooks.rb:100 0.000