Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 7 25 Apr 2025, 14:26

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:32.967 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:31.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 34.338
When I start Tails from USB drive "old" with network unplugged 1:51.680
Then the boot device has safe access rights 3.355
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.956
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login 1:30.419
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 38.365
And I take note of which tps features are available 9.175
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 8.602
After features/support/hooks.rb:330 0.232
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.650
Then Tails is running from USB drive "old" 0.545
And all tps features are active 2.938
When I write some files expected to persist 2.292
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.701
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.036
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.603
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 without a persistent partition and stopped at Tails Greeter's login screen 11.915
And I log in to a new session 20.386
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.824
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.861
Then the running Tails is installed on USB drive "to_upgrade" 27.624
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.280
After features/support/hooks.rb:330 1.059
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.709
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.406
And the boot device has safe access rights 4.592
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.719
After features/support/hooks.rb:330 1.068
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:48.116
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 13.963
And no SquashFS delta is installed 0.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.691
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.091
And Tor is ready 22.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.003
Given I shutdown Tails and wait for the computer to power off 8.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.187
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.378
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.362
When the network is plugged 0.088
And Tor is ready 18.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.261
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.243
Given I shutdown Tails and wait for the computer to power off 4.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.959
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.111
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.437
When the network is plugged 0.068
And Tor is ready 20.149
Then the Upgrader considers the system as up-to-date 0.369
# 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.160
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.172
After features/support/hooks.rb:330 0.674
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.479
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.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.710
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.155
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
After features/support/hooks.rb:330 0.678
After features/support/hooks.rb:100 0.000