Project Number Date
test_Tails_ISO_stable 5589 23 Apr 2025, 13:38

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:39.213 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.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.071
When I start Tails from USB drive "old" with network unplugged 1:24.742
Then the boot device has safe access rights 3.287
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.775
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.128
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:25.587
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 32.154
And I take note of which tps features are available 1.755
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.263
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.250
Then Tails is running from USB drive "old" 0.605
And all tps features are active 2.080
When I write some files expected to persist 1.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.584
And all persistent directories from the old Tails version have safe access rights 3.380
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 6.775
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.200
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.012
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 without a persistent partition and stopped at Tails Greeter's login screen 11.250
And I log in to a new session 20.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.989
And I plug USB drive "to_upgrade" 2.606
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.947
Then the running Tails is installed on USB drive "to_upgrade" 26.517
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.025
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.248
Then all tps features from the old Tails version are active 1.841
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.404
And the expected persistent files created with the old Tails version are present in the filesystem 1.762
And all persistent directories from the old Tails version have safe access rights 2.421
After features/support/hooks.rb:330 1.433
After features/support/hooks.rb:100 0.008
6:53.170
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 11.884
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.566
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.083
And Tor is ready 22.110
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.792
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.363
Given I shutdown Tails and wait for the computer to power off 11.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.879
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 7.530
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.370
# 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.266
When the network is plugged 0.570
And Tor is ready 21.790
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.105
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.083
Given I shutdown Tails and wait for the computer to power off 4.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.710
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.110
And Tor is ready 20.700
Then the Upgrader considers the system as up-to-date 0.373
# 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 16.531
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.869
After features/support/hooks.rb:330 0.882
After features/support/hooks.rb:100 0.019
40.489
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 12.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.129
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 23.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.992
After features/support/hooks.rb:330 1.078
After features/support/hooks.rb:100 0.000