Project Number Date
test_Tails_ISO_stable 5676 26 May 2025, 08:56

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:33.613 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.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.760
When I start Tails from USB drive "old" with network unplugged 1:30.821
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.535
After features/support/hooks.rb:100 0.016
Tags: @product
2:12.232
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:28.645
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 32.025
And I take note of which tps features are available 1.958
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.252
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.360
When I write some files expected to persist 1.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.450
And I take note of which tps features are available 0.495
And I shutdown Tails and wait for the computer to power off 4.444
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.599
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.317
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.038
And I log in to a new session 18.056
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.630
And I plug USB drive "to_upgrade" 2.528
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.342
Then the running Tails is installed on USB drive "to_upgrade" 28.234
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 3.157
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.909
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.709
Then all tps features from the old Tails version are active 3.192
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.491
After features/support/hooks.rb:330 0.642
After features/support/hooks.rb:100 0.008
6:52.848
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 11.570
And no SquashFS delta is installed 0.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.088
And Tor is ready 20.899
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.942
Given I shutdown Tails and wait for the computer to power off 8.932
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.386
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.284
# 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.322
When the network is plugged 0.072
And Tor is ready 20.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.531
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.853
Given I shutdown Tails and wait for the computer to power off 4.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.495
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.530
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.426
When the network is plugged 0.072
And Tor is ready 19.953
Then the Upgrader considers the system as up-to-date 0.350
# 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 17.535
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.878
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.017
38.060
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 10.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
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.096
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 20.736
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.369
After features/support/hooks.rb:330 0.758
After features/support/hooks.rb:100 0.000