Project Number Date
test_Tails_ISO_devel 3799 01 May 2025, 19:37

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:45.777 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:0.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.662
When I start Tails from USB drive "old" with network unplugged 1:24.452
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 0.993
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:24.770
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 31.006
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.088
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.345
Then Tails is running from USB drive "old" 0.383
And all tps features are active 1.955
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.332
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.789
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 4.423
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.169
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.251
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 12.265
And I log in to a new session 20.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.842
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.227
Then the running Tails is installed on USB drive "to_upgrade" 25.673
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 3.575
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.647
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.366
And the expected persistent files created with the old Tails version are present in the filesystem 1.680
And all persistent directories from the old Tails version have safe access rights 2.518
After features/support/hooks.rb:330 1.280
After features/support/hooks.rb:100 0.009
7:7.123
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 11.177
And no SquashFS delta is installed 0.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.508
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.062
And Tor is ready 50.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.599
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.144
Given I shutdown Tails and wait for the computer to power off 8.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.657
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.168
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.270
When the network is plugged 0.083
And Tor is ready 23.434
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.496
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.795
Given I shutdown Tails and wait for the computer to power off 4.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.031
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.100
And Tor is ready 19.935
Then the Upgrader considers the system as up-to-date 0.321
# 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.990
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.676
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.019
37.304
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.256
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.201
After features/support/hooks.rb:330 1.297
After features/support/hooks.rb:100 0.000