Project Number Date
test_Tails_ISO_stable 5578 16 Apr 2025, 12:51

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:34.528 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:52.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 28.281
When I start Tails from USB drive "old" with network unplugged 1:18.908
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:330 3.743
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:28.377
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 31.454
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 8.297
After features/support/hooks.rb:330 0.219
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.371
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 with persistence enabled 2:10.367
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.874
When I write some files expected to persist 1.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.386
And I take note of which tps features are available 0.396
And I shutdown Tails and wait for the computer to power off 4.644
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.657
After features/support/hooks.rb:330 0.087
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.339
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 without a persistent partition and stopped at Tails Greeter's login screen 9.905
And I log in to a new session 17.349
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.836
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.206
Then the running Tails is installed on USB drive "to_upgrade" 25.233
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:330 1.094
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.551
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:5.397
Then all tps features from the old Tails version are active 1.556
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.385
And the expected persistent files created with the old Tails version are present in the filesystem 1.433
And all persistent directories from the old Tails version have safe access rights 2.289
After features/support/hooks.rb:330 1.105
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.806
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 11.125
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.063
And Tor is ready 21.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.804
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.295
Given I shutdown Tails and wait for the computer to power off 8.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.968
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.062
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.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.251
When the network is plugged 0.068
And Tor is ready 19.674
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.480
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.641
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.922
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.907
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.063
And Tor is ready 16.178
Then the Upgrader considers the system as up-to-date 0.348
# 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.826
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.533
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.064
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 9.695
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.386
After features/support/hooks.rb:330 0.917
After features/support/hooks.rb:100 0.000