Project Number Date
test_Tails_ISO_devel 3781 13 Apr 2025, 13:08

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:55.100 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:11.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.161
And I write an old version of the Tails USB image to disk "old" 32.719
When I start Tails from USB drive "old" with network unplugged 1:33.225
Then the boot device has safe access rights 3.413
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 7.847
After features/support/hooks.rb:100 0.021
Tags: @product
2:8.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:25.577
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.676
And I take note of which tps features are available 1.722
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.532
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.278
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.307
Then Tails is running from USB drive "old" 0.843
And all tps features are active 2.196
When I write some files expected to persist 2.064
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.946
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.499
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.585
After features/support/hooks.rb:330 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.911
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 14.022
And I log in to a new session 30.082
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.321
And I plug USB drive "to_upgrade" 2.604
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.584
Then the running Tails is installed on USB drive "to_upgrade" 26.843
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 0.955
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.745
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:7.530
Then all tps features from the old Tails version are active 1.993
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.713
And all persistent directories from the old Tails version have safe access rights 2.484
After features/support/hooks.rb:330 1.179
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.659
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 11.185
And no SquashFS delta is installed 0.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.514
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.143
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.063
And Tor is ready 18.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.275
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.145
Given I shutdown Tails and wait for the computer to power off 8.722
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.077
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.753
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.285
When the network is plugged 0.073
And Tor is ready 19.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.929
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.017
Given I shutdown Tails and wait for the computer to power off 6.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.819
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.596
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.073
And Tor is ready 16.688
Then the Upgrader considers the system as up-to-date 0.361
# 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.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.007
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
53.138
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 24.597
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.458
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.301
And Tor is ready 18.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.699
After features/support/hooks.rb:330 1.057
After features/support/hooks.rb:100 0.000