Project Number Date
test_Tails_ISO_stable 5633 07 May 2025, 21:15

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:42.573 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:8.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.650
And I create a 7200 MiB disk named "old" 0.252
And I plug USB drive "old" 1.193
And I write an old version of the Tails USB image to disk "old" 30.666
When I start Tails from USB drive "old" with network unplugged 1:31.823
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 0.951
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.575
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:28.665
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 31.040
And I take note of which tps features are available 2.096
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.532
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.342
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.064
When I write some files expected to persist 1.607
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.396
And I take note of which tps features are available 0.414
And I shutdown Tails and wait for the computer to power off 4.339
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.188
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.012
Tags: @product
2:36.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.377
And I log in to a new session 19.987
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.901
And I plug USB drive "to_upgrade" 2.366
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.813
Then the running Tails is installed on USB drive "to_upgrade" 26.001
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 1.956
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.396
Then all tps features from the old Tails version are active 1.715
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.217
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.813
After features/support/hooks.rb:330 1.434
After features/support/hooks.rb:100 0.008
6:55.523
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.225
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.548
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.569
When the network is plugged 0.080
And Tor is ready 49.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.639
Given I shutdown Tails and wait for the computer to power off 8.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.786
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.300
When the network is plugged 0.068
And Tor is ready 18.490
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.097
Given I shutdown Tails and wait for the computer to power off 6.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.151
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.436
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.074
And Tor is ready 18.802
Then the Upgrader considers the system as up-to-date 0.423
# 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.379
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.749
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.022
38.043
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.031
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.524
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.094
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 19.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.053
After features/support/hooks.rb:330 0.694
After features/support/hooks.rb:100 0.000