Project Number Date
test_Tails_ISO_improved-new-identity-scenario 18 17 May 2025, 13:24

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:21.104 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:5.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.191
When I start Tails from USB drive "old" with network unplugged 1:30.045
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 6.962
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:28.700
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.606
And I take note of which tps features are available 1.833
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.310
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.272
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 with persistence enabled 2:18.501
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.039
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.238
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 4.348
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.896
After features/support/hooks.rb:330 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.599
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 9.667
And I log in to a new session 18.880
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.614
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.673
Then the running Tails is installed on USB drive "to_upgrade" 22.965
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 6.688
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.262
Then all tps features from the old Tails version are active 1.704
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.644
And the expected persistent files created with the old Tails version are present in the filesystem 1.361
And all persistent directories from the old Tails version have safe access rights 2.341
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.021
6:46.561
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 13.664
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.125
And Tor is ready 19.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.101
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.315
Given I shutdown Tails and wait for the computer to power off 8.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.535
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.073
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.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.263
When the network is plugged 0.076
And Tor is ready 19.342
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.892
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.111
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.834
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
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.274
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.065
And Tor is ready 20.020
Then the Upgrader considers the system as up-to-date 0.310
# 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.847
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.817
After features/support/hooks.rb:330 0.967
After features/support/hooks.rb:100 0.015
38.450
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.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.505
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 19.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.153
After features/support/hooks.rb:330 2.286
After features/support/hooks.rb:100 0.000