Project Number Date
test_Tails_ISO_stable 5553 04 Apr 2025, 09:43

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:50.365 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:7.182
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.819
When I start Tails from USB drive "old" with network unplugged 1:31.118
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:330 7.206
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:30.553
Then Tails is running from USB drive "old" 0.445
And I create a persistent partition 32.071
And I take note of which tps features are available 1.655
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.017
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.161
Then Tails is running from USB drive "old" 0.431
And all tps features are active 2.160
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.316
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.344
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.359
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 24.828
And I log in to a new session 20.232
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.692
Then the running Tails is installed on USB drive "to_upgrade" 23.179
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 1.861
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.907
Then all tps features from the old Tails version are active 1.795
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.220
And the expected persistent files created with the old Tails version are present in the filesystem 1.714
And all persistent directories from the old Tails version have safe access rights 2.498
After features/support/hooks.rb:330 1.380
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:48.222
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 13.084
And no SquashFS delta is installed 0.225
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.086
And Tor is ready 24.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.870
Given I shutdown Tails and wait for the computer to power off 8.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.278
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.480
When the network is plugged 0.075
And Tor is ready 19.537
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.986
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.180
Given I shutdown Tails and wait for the computer to power off 6.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.088
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.676
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.068
And Tor is ready 18.507
Then the Upgrader considers the system as up-to-date 0.358
# 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.861
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.412
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
43.850
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.247
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.255
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.105
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 23.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.457
After features/support/hooks.rb:330 0.903
After features/support/hooks.rb:100 0.000