Project Number Date
test_Tails_ISO_stable 4988 01 Aug 2024, 14:00

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 22:41.428 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
3:1.764
Before features/support/hooks.rb:269 0.004
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.086
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 1:9.964
When I start Tails from USB drive "old" with network unplugged 1:44.388
Then the boot device has safe access rights 4.614
And Tails is running from USB drive "old" 0.420
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.463
And I unplug USB drive "old" 0.278
After features/support/hooks.rb:326 8.847
After features/support/hooks.rb:100 0.013
Tags: @product
2:15.461
Before features/support/hooks.rb:269 0.010
Given a computer 0.277
And I start Tails from USB drive "old" with network unplugged and I login 1:28.066
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 35.174
And I take note of which tps features are available 1.883
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.848
After features/support/hooks.rb:326 0.254
After features/support/hooks.rb:100 0.012
Tags: @product
3:9.902
Before features/support/hooks.rb:269 0.007
Given a computer 0.304
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.347
Then Tails is running from USB drive "old" 0.459
And all tps features are active 2.851
When I write some files expected to persist 2.141
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.370
And all persistence configuration files have safe access rights 0.585
And all persistent directories from the old Tails version have safe access rights 2.892
And I take note of which tps features are available 0.623
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.027
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.011
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.210
And I log in to a new session 22.646
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.873
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.915
Then the running Tails is installed on USB drive "to_upgrade" 25.380
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:326 2.676
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.502
Before features/support/hooks.rb:269 0.008
Given a computer 0.278
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.255
Then all tps features from the old Tails version are active 2.629
And Tails is running from USB drive "to_upgrade" 0.444
And the boot device has safe access rights 4.124
And the expected persistent files created with the old Tails version are present in the filesystem 1.744
And all persistent directories from the old Tails version have safe access rights 3.025
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:25.372
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.089
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.550
When the network is plugged 0.110
And Tor is ready 24.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.970
Given I shutdown Tails and wait for the computer to power off 10.774
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.910
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 8.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.330
When the network is plugged 0.283
And Tor is ready 21.389
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.699
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.284
Given I shutdown Tails and wait for the computer to power off 6.830
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.566
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.592
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.057
And Tor is ready 18.980
Then the Upgrader considers the system as up-to-date 0.359
# 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.929
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.210
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
1:3.413
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.958
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.933
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 50.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.665
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.000