Project Number Date
test_Tails_ISO_stable 5435 31 Jan 2025, 12: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 18:48.974 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
1:57.996
Before features/support/hooks.rb:269 0.004
Given a computer 0.282
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.393
When I start Tails from USB drive "old" with network unplugged 1:21.264
Then the boot device has safe access rights 3.011
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.541
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.138
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:20.672
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 30.084
And I take note of which tps features are available 1.331
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 8.669
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.937
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.829
Then Tails is running from USB drive "old" 1.178
And all tps features are active 2.109
When I write some files expected to persist 1.703
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 4.034
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.396
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.945
Before features/support/hooks.rb:269 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 9.971
And I log in to a new session 19.347
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.483
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.468
Then the running Tails is installed on USB drive "to_upgrade" 16.861
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 6.980
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.504
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.313
Then all tps features from the old Tails version are active 1.595
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.036
And the expected persistent files created with the old Tails version are present in the filesystem 1.533
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.849
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:43.500
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.428
And no SquashFS delta is installed 0.331
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.114
And Tor is ready 21.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.522
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.956
Given I shutdown Tails and wait for the computer to power off 8.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.132
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.318
When the network is plugged 0.104
And Tor is ready 49.221
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.875
Given I shutdown Tails and wait for the computer to power off 4.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.229
Then Tails is running version 6.3~testoverlayfs 0.042
And all tps features are active 1.951
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.095
And Tor is ready 19.364
Then the Upgrader considers the system as up-to-date 0.385
# 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 14.487
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.952
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.271
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.593
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.424
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.000