Project Number Date
test_Tails_ISO_stable 5338 16 Dec 2024, 12:35

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:55.086 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:56.208
Before features/support/hooks.rb:269 0.003
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.676
When I start Tails from USB drive "old" with network unplugged 1:22.403
Then the boot device has safe access rights 2.907
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 6.996
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.176
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:22.791
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 32.040
And I take note of which tps features are available 1.367
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 6.601
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.179
Before features/support/hooks.rb:269 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.864
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.170
When I write some files expected to persist 2.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.199
And I take note of which tps features are available 0.683
And I shutdown Tails and wait for the computer to power off 4.618
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.732
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:24.694
Before features/support/hooks.rb:269 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 10.691
And I log in to a new session 18.850
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.580
And I plug USB drive "to_upgrade" 2.352
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.554
Then the running Tails is installed on USB drive "to_upgrade" 17.247
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 6.892
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.845
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.963
Then all tps features from the old Tails version are active 1.572
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.144
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:326 1.027
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:44.626
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.610
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.096
And Tor is ready 48.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.080
Given I shutdown Tails and wait for the computer to power off 8.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.920
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.909
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.431
# 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.420
When the network is plugged 0.068
And Tor is ready 18.307
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.562
Given I shutdown Tails and wait for the computer to power off 4.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.935
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.036
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.068
And Tor is ready 15.270
Then the Upgrader considers the system as up-to-date 10.760
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.896
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.356
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.714
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 21.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.369
After features/support/hooks.rb:326 0.640
After features/support/hooks.rb:100 0.000