Project Number Date
test_Tails_ISO_devel 3849 02 Jun 2025, 16: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:16.555 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:27.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.585
When I start Tails from USB drive "old" with network unplugged 1:47.484
Then the boot device has safe access rights 3.472
And Tails is running from USB drive "old" 0.449
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 8.707
After features/support/hooks.rb:100 0.014
Tags: @product
2:24.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login 1:36.198
Then Tails is running from USB drive "old" 0.462
And I create a persistent partition 34.975
And I take note of which tps features are available 3.029
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 8.991
After features/support/hooks.rb:330 0.251
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.710
Then Tails is running from USB drive "old" 0.430
And all tps features are active 2.396
When I write some files expected to persist 2.067
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.349
And all persistence configuration files have safe access rights 0.545
And all persistent directories from the old Tails version have safe access rights 2.743
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 6.622
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.066
After features/support/hooks.rb:330 0.224
After features/support/hooks.rb:100 0.026
Tags: @product
2:41.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.770
And I log in to a new session 20.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.767
And I plug USB drive "to_upgrade" 2.631
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.242
Then the running Tails is installed on USB drive "to_upgrade" 24.353
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 6.976
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.844
Then all tps features from the old Tails version are active 3.314
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 3.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.572
And all persistent directories from the old Tails version have safe access rights 2.571
After features/support/hooks.rb:330 1.472
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:34.766
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 17.619
And no SquashFS delta is installed 0.322
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.554
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.069
And Tor is ready 25.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.533
Given I shutdown Tails and wait for the computer to power off 11.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.153
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.623
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.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.398
When the network is plugged 0.146
And Tor is ready 46.532
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.660
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.489
Given I shutdown Tails and wait for the computer to power off 1:5.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.049
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 3.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.342
And Tor is ready 21.363
Then the Upgrader considers the system as up-to-date 0.387
# 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.627
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.675
After features/support/hooks.rb:330 0.768
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
38.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.247
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.557
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 19.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.920
After features/support/hooks.rb:330 2.126
After features/support/hooks.rb:100 0.000