Project Number Date
test_Tails_ISO_stable 5411 22 Jan 2025, 08:51

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:3.311 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:59.177
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.100
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.012
When I start Tails from USB drive "old" with network unplugged 1:23.662
Then the boot device has safe access rights 3.085
And Tails is running from USB drive "old" 0.355
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.333
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 6.937
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.197
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:22.743
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 31.450
And I take note of which tps features are available 1.446
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.214
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.414
Before features/support/hooks.rb:269 0.004
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.692
Then Tails is running from USB drive "old" 0.385
And all tps features are active 1.986
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.459
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 4.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.385
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.047
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.795
And I log in to a new session 16.757
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.598
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.171
Then the running Tails is installed on USB drive "to_upgrade" 24.919
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 1.957
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.972
Before features/support/hooks.rb:269 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 1:57.098
Then all tps features from the old Tails version are active 1.551
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 3.012
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.215
After features/support/hooks.rb:326 0.966
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:3.026
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.390
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.089
And Tor is ready 19.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.019
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.403
Given I shutdown Tails and wait for the computer to power off 8.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.578
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.334
When the network is plugged 0.081
And Tor is ready 17.462
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.263
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.758
Given I shutdown Tails and wait for the computer to power off 4.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.713
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.874
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.087
And Tor is ready 17.288
Then the Upgrader considers the system as up-to-date 0.303
# 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.432
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.927
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.477
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.739
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.375
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.000