Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 6 24 Apr 2025, 21:38

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 22:3.670 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:29.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.121
When I start Tails from USB drive "old" with network unplugged 1:51.589
Then the boot device has safe access rights 3.306
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.809
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.309
And I start Tails from USB drive "old" with network unplugged and I login 1:45.480
Then Tails is running from USB drive "old" 0.426
And I create a persistent partition 33.232
And I take note of which tps features are available 1.789
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.507
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.009
Tags: @product
3:26.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:49.374
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.002
When I write some files expected to persist 1.828
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.512
And all persistent directories from the old Tails version have safe access rights 2.617
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.507
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.962
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.673
And I log in to a new session 21.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.789
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.188
Then the running Tails is installed on USB drive "to_upgrade" 26.959
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 2.454
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.376
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.862
Then all tps features from the old Tails version are active 1.861
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.624
And all persistent directories from the old Tails version have safe access rights 2.658
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.010
7:43.219
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 12.008
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.071
And Tor is ready 21.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.649
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.948
Given I shutdown Tails and wait for the computer to power off 11.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.560
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.705
And the file system changes introduced in version 6.2~testoverlayfs are present 0.442
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.447
When the network is plugged 0.078
And Tor is ready 20.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.427
Given I shutdown Tails and wait for the computer to power off 6.992
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.900
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.362
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.400
When the network is plugged 0.072
And Tor is ready 46.798
Then the Upgrader considers the system as up-to-date 0.682
# 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.387
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.619
After features/support/hooks.rb:330 0.904
After features/support/hooks.rb:100 0.025
42.523
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 11.480
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.468
And Tor is ready 21.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.561
After features/support/hooks.rb:330 1.096
After features/support/hooks.rb:100 0.000