Project Number Date
test_Tails_ISO_devel 3829 22 May 2025, 09:46

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:16.440 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.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 35.926
When I start Tails from USB drive "old" with network unplugged 1:33.244
Then the boot device has safe access rights 3.240
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.124
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.904
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:27.927
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 33.544
And I take note of which tps features are available 1.703
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.375
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.340
Then Tails is running from USB drive "old" 0.317
And all tps features are active 2.063
When I write some files expected to persist 1.717
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 3.876
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 6.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.900
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.424
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 11.052
And I log in to a new session 19.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.656
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.784
Then the running Tails is installed on USB drive "to_upgrade" 23.658
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.299
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.488
Then all tps features from the old Tails version are active 1.700
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.540
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.491
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:32.428
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.362
And no SquashFS delta is installed 0.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
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.486
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.500
When the network is plugged 0.069
And Tor is ready 19.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.906
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.300
Given I shutdown Tails and wait for the computer to power off 1:12.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.401
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.105
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.317
When the network is plugged 0.069
And Tor is ready 20.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.779
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.240
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.383
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.067
And Tor is ready 17.574
Then the Upgrader considers the system as up-to-date 0.309
# 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.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.362
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.804
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 with a persistent partition enabled and logged in 10.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.174
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 20.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.774
After features/support/hooks.rb:330 0.697
After features/support/hooks.rb:100 0.000