Project Number Date
test_Tails_ISO_stable 5482 26 Feb 2025, 19:55

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:28.911 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:6.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.337
When I start Tails from USB drive "old" with network unplugged 1:30.675
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:330 3.503
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:23.507
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.720
And I take note of which tps features are available 1.950
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.330
After features/support/hooks.rb:330 0.287
After features/support/hooks.rb:100 0.007
Tags: @product
2:56.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.604
Then Tails is running from USB drive "old" 0.515
And all tps features are active 2.008
When I write some files expected to persist 2.948
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.759
And all persistent directories from the old Tails version have safe access rights 2.581
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 6.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.523
After features/support/hooks.rb:330 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.767
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 without a persistent partition and stopped at Tails Greeter's login screen 9.012
And I log in to a new session 18.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.359
And I plug USB drive "to_upgrade" 2.368
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.201
Then the running Tails is installed on USB drive "to_upgrade" 20.123
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 6.653
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.261
Then all tps features from the old Tails version are active 2.039
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.738
And all persistent directories from the old Tails version have safe access rights 2.564
After features/support/hooks.rb:330 1.049
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.716
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 10.421
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.074
And Tor is ready 23.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.904
Given I shutdown Tails and wait for the computer to power off 8.709
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.523
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.305
And the file system changes introduced in version 6.2~testoverlayfs are present 0.475
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.262
When the network is plugged 0.063
And Tor is ready 46.461
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.389
Given I shutdown Tails and wait for the computer to power off 4.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.351
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.071
And Tor is ready 19.538
Then the Upgrader considers the system as up-to-date 0.327
# 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.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.055
After features/support/hooks.rb:330 0.708
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.241
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 9.533
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.101
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 18.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.623
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.000