Project Number Date
test_Tails_ISO_stable 5741 26 Jun 2025, 13:11

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 20:32.090 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:18.538
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.090
And I plug USB drive "old" 1.101
And I write an old version of the Tails USB image to disk "old" 32.479
When I start Tails from USB drive "old" with network unplugged 1:40.026
Then the boot device has safe access rights 3.499
And Tails is running from USB drive "old" 0.425
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.526
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:29.680
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 31.520
And I take note of which tps features are available 2.244
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 9.803
After features/support/hooks.rb:330 0.227
After features/support/hooks.rb:100 0.010
Tags: @product
3:10.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.731
Then Tails is running from USB drive "old" 0.458
And all tps features are active 2.009
When I write some files expected to persist 2.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 3.700
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.467
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.646
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.028
Tags: @product
2:43.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.744
And I log in to a new session 20.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.529
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.398
Then the running Tails is installed on USB drive "to_upgrade" 29.182
And I unplug USB drive "to_upgrade" 0.269
And I unplug USB drive "__internal" 0.299
After features/support/hooks.rb:330 2.427
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.351
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.989
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 4.064
And the expected persistent files created with the old Tails version are present in the filesystem 1.943
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:330 1.231
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
7:1.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.938
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.712
When the network is plugged 0.435
And Tor is ready 22.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.067
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.919
Given I shutdown Tails and wait for the computer to power off 8.985
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.671
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.326
When the network is plugged 0.088
And Tor is ready 19.179
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.965
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.832
Given I shutdown Tails and wait for the computer to power off 4.856
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.903
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.645
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.079
And Tor is ready 20.719
Then the Upgrader considers the system as up-to-date 0.367
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.582
After features/support/hooks.rb:330 0.697
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.045
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.013
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 24.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.863
After features/support/hooks.rb:330 0.597
After features/support/hooks.rb:100 0.000