Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 4 23 Apr 2025, 21:30

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:59.852 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.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 34.355
When I start Tails from USB drive "old" with network unplugged 1:36.747
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.430
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.304
After features/support/hooks.rb:330 3.817
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.142
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:40.194
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 30.801
And I take note of which tps features are available 2.179
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.601
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.014
Tags: @product
2:58.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.144
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.875
When I write some files expected to persist 2.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.392
And I take note of which tps features are available 0.367
And I shutdown Tails and wait for the computer to power off 4.471
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.207
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.557
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 12.210
And I log in to a new session 20.146
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.085
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.849
Then the running Tails is installed on USB drive "to_upgrade" 25.377
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 2.274
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.621
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.572
After features/support/hooks.rb:330 1.114
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:47.015
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.576
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.153
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.080
And Tor is ready 23.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.075
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.833
Given I shutdown Tails and wait for the computer to power off 8.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.425
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.041
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.303
When the network is plugged 0.071
And Tor is ready 17.162
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.846
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.936
Given I shutdown Tails and wait for the computer to power off 6.553
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.021
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.672
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.064
And Tor is ready 19.095
Then the Upgrader considers the system as up-to-date 10.976
# 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.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.829
After features/support/hooks.rb:330 0.736
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.168
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 with a persistent partition enabled and logged in 11.011
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.393
After features/support/hooks.rb:330 1.632
After features/support/hooks.rb:100 0.000