Project Number Date
test_Tails_ISO_stable 5585 20 Apr 2025, 12:44

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:55.609 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:6.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.441
When I start Tails from USB drive "old" with network unplugged 1:29.971
Then the boot device has safe access rights 3.043
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.537
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.137
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:23.901
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 33.001
And I take note of which tps features are available 2.027
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.891
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.014
Tags: @product
2:46.530
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.209
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.041
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.524
And all persistent directories from the old Tails version have safe access rights 2.450
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 6.227
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.001
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.725
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.779
And I log in to a new session 18.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.751
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.345
Then the running Tails is installed on USB drive "to_upgrade" 20.501
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.611
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.235
Then all tps features from the old Tails version are active 1.789
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.130
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.733
After features/support/hooks.rb:330 1.580
After features/support/hooks.rb:100 0.008
6:26.887
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.811
And no SquashFS delta is installed 0.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.073
And Tor is ready 21.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.158
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.917
Given I shutdown Tails and wait for the computer to power off 8.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.928
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.387
# 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.061
And Tor is ready 16.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.731
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.434
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.056
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.070
And Tor is ready 20.108
Then the Upgrader considers the system as up-to-date 0.301
# 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.940
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.503
After features/support/hooks.rb:330 0.757
After features/support/hooks.rb:100 0.017
35.772
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 10.417
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.997
After features/support/hooks.rb:330 0.601
After features/support/hooks.rb:100 0.000