Project Number Date
test_Tails_ISO_devel 3772 09 Apr 2025, 14:16

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:23.945 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:19.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.926
When I start Tails from USB drive "old" with network unplugged 1:41.789
Then the boot device has safe access rights 3.351
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:330 1.095
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:28.759
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 32.792
And I take note of which tps features are available 2.353
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.807
After features/support/hooks.rb:330 0.204
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.072
Then Tails is running from USB drive "old" 0.398
And all tps features are active 2.331
When I write some files expected to persist 2.152
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.529
And all persistent directories from the old Tails version have safe access rights 2.803
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.812
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.029
Tags: @product
2:44.275
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 without a persistent partition and stopped at Tails Greeter's login screen 11.905
And I log in to a new session 23.637
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.230
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.105
Then the running Tails is installed on USB drive "to_upgrade" 27.365
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.288
After features/support/hooks.rb:330 1.124
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.553
Then all tps features from the old Tails version are active 1.931
And Tails is running from USB drive "to_upgrade" 0.472
And the boot device has safe access rights 3.611
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 2.689
After features/support/hooks.rb:330 1.173
After features/support/hooks.rb:100 0.010
6:58.432
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 15.733
And no SquashFS delta is installed 0.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.408
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.069
And Tor is ready 17.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.722
Given I shutdown Tails and wait for the computer to power off 11.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.397
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.709
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# 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.298
When the network is plugged 0.103
And Tor is ready 23.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.861
Given I shutdown Tails and wait for the computer to power off 7.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.388
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 2.073
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.069
And Tor is ready 19.071
Then the Upgrader considers the system as up-to-date 0.375
# 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 16.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.199
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.025
38.815
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 with a persistent partition enabled and logged in 11.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.568
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.098
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 20.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.762
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.000