Project Number Date
test_Tails_ISO_stable 5580 17 Apr 2025, 12:47

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 18:53.007 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
1:58.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.768
When I start Tails from USB drive "old" with network unplugged 1:23.185
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:330 3.494
After features/support/hooks.rb:100 0.042
Tags: @product
2:7.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:24.798
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 31.433
And I take note of which tps features are available 1.500
Then a Tails persistence partition exists on USB drive "old" 0.724
And I shutdown Tails and wait for the computer to power off 8.247
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.371
Then Tails is running from USB drive "old" 0.940
And all tps features are active 2.122
When I write some files expected to persist 1.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.589
And all persistent directories from the old Tails version have safe access rights 2.991
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.239
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.277
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.963
And I log in to a new session 18.836
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.867
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.567
Then the running Tails is installed on USB drive "to_upgrade" 24.229
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.905
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.809
Then all tps features from the old Tails version are active 1.639
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.061
And the expected persistent files created with the old Tails version are present in the filesystem 1.338
And all persistent directories from the old Tails version have safe access rights 2.285
After features/support/hooks.rb:330 1.312
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.748
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.667
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.062
And Tor is ready 21.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.043
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.948
Given I shutdown Tails and wait for the computer to power off 10.779
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.477
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.299
When the network is plugged 0.082
And Tor is ready 19.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.316
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.232
Given I shutdown Tails and wait for the computer to power off 4.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.126
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.163
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.070
And Tor is ready 16.931
Then the Upgrader considers the system as up-to-date 0.315
# 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.462
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.384
After features/support/hooks.rb:330 0.830
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.462
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 9.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.703
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.424
After features/support/hooks.rb:330 0.710
After features/support/hooks.rb:100 0.000