Project Number Date
test_Tails_ISO_stable 5530 25 Mar 2025, 12:53

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:56.368 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.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.229
When I start Tails from USB drive "old" with network unplugged 1:45.051
Then the boot device has safe access rights 3.231
And Tails is running from USB drive "old" 0.441
And there is no persistence partition on USB drive "old" 0.320
And process "udev-watchdog" is running 0.291
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.684
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:29.383
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 30.982
And I take note of which tps features are available 1.749
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.132
Then Tails is running from USB drive "old" 0.462
And all tps features are active 2.288
When I write some files expected to persist 1.872
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.839
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.493
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.170
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.484
And I log in to a new session 19.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.580
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.072
Then the running Tails is installed on USB drive "to_upgrade" 25.618
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 1.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.495
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.519
Then all tps features from the old Tails version are active 1.696
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.686
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.577
After features/support/hooks.rb:330 1.780
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:29.857
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 11.301
And no SquashFS delta is installed 0.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.087
And Tor is ready 21.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.777
Given I shutdown Tails and wait for the computer to power off 8.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.287
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
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.390
# 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.360
When the network is plugged 0.084
And Tor is ready 17.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.446
Given I shutdown Tails and wait for the computer to power off 4.434
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.455
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.075
And Tor is ready 18.942
Then the Upgrader considers the system as up-to-date 0.312
# 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 14.707
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:330 0.810
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
40.083
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.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 22.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.274
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.000