Project Number Date
test_Tails_ISO_devel 3803 06 May 2025, 19:50

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 21:1.595 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:16.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.124
And I write an old version of the Tails USB image to disk "old" 31.016
When I start Tails from USB drive "old" with network unplugged 1:40.424
Then the boot device has safe access rights 3.054
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.759
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:25.941
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 32.743
And I take note of which tps features are available 1.935
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.514
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.082
Then Tails is running from USB drive "old" 0.500
And all tps features are active 1.853
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.420
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.676
And I take note of which tps features are available 0.381
And I shutdown Tails and wait for the computer to power off 4.440
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.986
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.284
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 11.844
And I log in to a new session 21.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.005
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.396
Then the running Tails is installed on USB drive "to_upgrade" 25.674
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 2.101
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.993
Then all tps features from the old Tails version are active 1.795
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.674
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.517
After features/support/hooks.rb:330 0.946
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:1.269
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 11.839
And no SquashFS delta is installed 0.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.494
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.079
And Tor is ready 21.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.319
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.712
Given I shutdown Tails and wait for the computer to power off 1:27.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.173
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# 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.302
When the network is plugged 0.078
And Tor is ready 18.706
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.744
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.873
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.110
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 2.568
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.120
And Tor is ready 17.697
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 15.719
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.535
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.745
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 9.433
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.160
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 19.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.361
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.000