Project Number Date
test_Tails_ISO_stable 5406 21 Jan 2025, 08:33

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:33.321 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:51.812
Before features/support/hooks.rb:269 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.130
When I start Tails from USB drive "old" with network unplugged 1:17.550
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 6.794
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.432
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:20.125
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 31.749
And I take note of which tps features are available 1.362
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.955
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.236
Before features/support/hooks.rb:269 0.003
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.340
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.133
When I write some files expected to persist 1.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.659
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.253
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.770
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.512
And I log in to a new session 17.809
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.566
Then the running Tails is installed on USB drive "to_upgrade" 19.566
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.309
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.348
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.481
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.149
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:326 0.911
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:44.332
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.510
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
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.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.071
And Tor is ready 23.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.360
Given I shutdown Tails and wait for the computer to power off 12.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.052
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.114
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.267
When the network is plugged 0.070
And Tor is ready 15.844
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.719
Given I shutdown Tails and wait for the computer to power off 4.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.073
Then Tails is running version 6.3~testoverlayfs 0.056
And all tps features are active 2.079
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.081
And Tor is ready 43.812
Then the Upgrader considers the system as up-to-date 0.313
# 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.441
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.914
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
35.389
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.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 17.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.468
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.000