Project Number Date
test_Tails_ISO_stable 5699 05 Jun 2025, 12:48

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:36.068 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:14.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.004
When I start Tails from USB drive "old" with network unplugged 1:36.745
Then the boot device has safe access rights 3.480
And Tails is running from USB drive "old" 0.425
And there is no persistence partition on USB drive "old" 0.103
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.784
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:28.941
Then Tails is running from USB drive "old" 0.497
And I create a persistent partition 32.452
And I take note of which tps features are available 2.618
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 9.119
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.007
Tags: @product
3:5.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.071
Then Tails is running from USB drive "old" 0.499
And all tps features are active 2.019
When I write some files expected to persist 1.890
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.606
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 6.653
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.930
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.531
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 10.945
And I log in to a new session 22.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.198
And I plug USB drive "to_upgrade" 2.597
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.279
Then the running Tails is installed on USB drive "to_upgrade" 25.441
And I unplug USB drive "to_upgrade" 0.285
And I unplug USB drive "__internal" 0.280
After features/support/hooks.rb:330 1.880
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.941
Then all tps features from the old Tails version are active 1.682
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 3.067
After features/support/hooks.rb:330 1.916
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:17.715
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.878
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.599
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.125
And Tor is ready 50.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.705
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.089
Given I shutdown Tails and wait for the computer to power off 9.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.774
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.286
When the network is plugged 0.106
And Tor is ready 17.355
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.694
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.060
Given I shutdown Tails and wait for the computer to power off 4.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.275
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.065
And Tor is ready 17.006
Then the Upgrader considers the system as up-to-date 10.871
# 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.086
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.569
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.815
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 10.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.550
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
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.064
And Tor is ready 18.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.803
After features/support/hooks.rb:330 0.879
After features/support/hooks.rb:100 0.000