Project Number Date
test_Tails_ISO_devel 3771 09 Apr 2025, 10:14

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:1.993 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:30.029
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.468
And I create a 7200 MiB disk named "old" 0.084
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 32.599
When I start Tails from USB drive "old" with network unplugged 1:51.328
Then the boot device has safe access rights 3.418
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 3.741
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login 1:25.550
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 33.240
And I take note of which tps features are available 2.307
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 10.788
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.845
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.070
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.397
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.352
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.989
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.387
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 12.349
And I log in to a new session 21.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.255
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.258
Then the running Tails is installed on USB drive "to_upgrade" 19.471
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.622
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.187
Then all tps features from the old Tails version are active 1.876
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.788
And the expected persistent files created with the old Tails version are present in the filesystem 1.511
And all persistent directories from the old Tails version have safe access rights 2.691
After features/support/hooks.rb:330 1.170
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:50.549
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 13.829
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.565
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.429
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.079
And Tor is ready 19.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.158
Given I shutdown Tails and wait for the computer to power off 8.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.101
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.219
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.337
When the network is plugged 0.080
And Tor is ready 19.641
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.543
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.840
Given I shutdown Tails and wait for the computer to power off 4.598
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.561
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.596
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.067
And Tor is ready 19.399
Then the Upgrader considers the system as up-to-date 0.364
# 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.508
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.564
After features/support/hooks.rb:330 0.711
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
37.940
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.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.424
After features/support/hooks.rb:330 1.350
After features/support/hooks.rb:100 0.000