Project Number Date
test_Tails_ISO_devel 3779 11 Apr 2025, 16:47

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:47.634 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:7.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.469
When I start Tails from USB drive "old" with network unplugged 1:29.734
Then the boot device has safe access rights 3.244
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 7.201
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:28.003
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 32.956
And I take note of which tps features are available 1.999
Then a Tails persistence partition exists on USB drive "old" 0.991
And I shutdown Tails and wait for the computer to power off 7.107
After features/support/hooks.rb:330 0.236
After features/support/hooks.rb:100 0.023
Tags: @product
2:58.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.174
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.099
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.522
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.646
And I shutdown Tails and wait for the computer to power off 4.621
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.045
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.051
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.635
And I log in to a new session 23.006
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.196
And I plug USB drive "to_upgrade" 2.489
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.374
Then the running Tails is installed on USB drive "to_upgrade" 21.930
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.053
Then all tps features from the old Tails version are active 1.641
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.451
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 2.422
After features/support/hooks.rb:330 0.946
After features/support/hooks.rb:100 0.010
7:3.688
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 with a persistent partition enabled and logged in 12.018
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.381
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.059
And Tor is ready 19.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.533
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.269
Given I shutdown Tails and wait for the computer to power off 8.824
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.631
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 6.143
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.325
When the network is plugged 0.074
And Tor is ready 47.561
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.839
Given I shutdown Tails and wait for the computer to power off 4.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.806
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.311
When the network is plugged 0.067
And Tor is ready 20.550
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 16.688
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.035
After features/support/hooks.rb:330 0.882
After features/support/hooks.rb:100 0.024
35.557
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 10.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.013
After features/support/hooks.rb:330 1.446
After features/support/hooks.rb:100 0.000