Project Number Date
test_Tails_ISO_stable 5569 11 Apr 2025, 16:02

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:26.427 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:23.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 37.188
When I start Tails from USB drive "old" with network unplugged 1:40.099
Then the boot device has safe access rights 4.010
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.399
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.605
After features/support/hooks.rb:100 0.015
Tags: @product
2:16.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.340
And I start Tails from USB drive "old" with network unplugged and I login 1:30.367
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 35.379
And I take note of which tps features are available 2.139
Then a Tails persistence partition exists on USB drive "old" 1.158
And I shutdown Tails and wait for the computer to power off 7.158
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.008
Tags: @product
3:13.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.124
Then Tails is running from USB drive "old" 0.906
And all tps features are active 2.315
When I write some files expected to persist 3.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.633
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.193
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.089
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.148
And I log in to a new session 21.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.690
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.237
Then the running Tails is installed on USB drive "to_upgrade" 27.077
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 6.806
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.207
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:6.174
Then all tps features from the old Tails version are active 1.685
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.886
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.385
After features/support/hooks.rb:330 1.515
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:2.882
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.358
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.689
When the network is plugged 0.114
And Tor is ready 18.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.958
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.058
Given I shutdown Tails and wait for the computer to power off 8.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.613
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
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.313
# 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.350
When the network is plugged 0.065
And Tor is ready 17.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.969
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.256
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.106
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.102
And Tor is ready 44.978
Then the Upgrader considers the system as up-to-date 0.322
# 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.972
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.715
After features/support/hooks.rb:330 0.768
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.037
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 9.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the signing key used by the Upgrader is outdated 0.153
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 17.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.904
After features/support/hooks.rb:330 1.530
After features/support/hooks.rb:100 0.000