Project Number Date
test_Tails_ISO_test-suite-options 1 17 Jun 2025, 01:12

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 29:2.254 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
3:18.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 47.220
When I start Tails from USB drive "old" with network unplugged 2:21.547
Then the boot device has safe access rights 7.738
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.826
After features/support/hooks.rb:100 0.020
Tags: @product
3:15.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.427
And I start Tails from USB drive "old" with network unplugged and I login 2:5.150
Then Tails is running from USB drive "old" 3.114
And I create a persistent partition 51.233
And I take note of which tps features are available 2.809
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 12.125
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.011
Tags: @product
4:19.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:19.458
Then Tails is running from USB drive "old" 0.725
And all tps features are active 2.232
When I write some files expected to persist 2.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 7.900
And I take note of which tps features are available 0.700
And I shutdown Tails and wait for the computer to power off 6.574
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.330
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.012
Tags: @product
3:22.915
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 14.937
And I log in to a new session 28.286
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.396
And I plug USB drive "to_upgrade" 2.865
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.268
Then the running Tails is installed on USB drive "to_upgrade" 36.692
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 3.823
After features/support/hooks.rb:100 0.000
Tags: @product
3:32.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.364
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:12.883
Then all tps features from the old Tails version are active 2.247
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 4.793
And the expected persistent files created with the old Tails version are present in the filesystem 7.283
And all persistent directories from the old Tails version have safe access rights 4.410
After features/support/hooks.rb:330 1.426
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
10:1.797
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 25.706
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.069
And Tor is ready 32.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.394
Given I shutdown Tails and wait for the computer to power off 18.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.743
Then Tails is running version 6.2~testoverlayfs 0.049
And all tps features are active 6.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.427
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.432
# 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.791
When the network is plugged 0.110
And Tor is ready 23.380
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 15.003
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.163
Given I shutdown Tails and wait for the computer to power off 10.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.556
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 3.544
And the file system changes introduced in version 6.3~testoverlayfs are present 0.623
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.360
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.088
And Tor is ready 31.811
Then the Upgrader considers the system as up-to-date 1.454
# 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 24.902
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.846
After features/support/hooks.rb:330 1.065
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
1:11.049
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 23.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.464
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 32.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.048
After features/support/hooks.rb:330 4.103
After features/support/hooks.rb:100 0.000