Project Number Date
test_Tails_ISO_stable 4857 28 May 2024, 16:39

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:22.137 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:47.250
Before features/support/hooks.rb:259 0.006
Given a computer 1.508
And I create a 7200 MiB disk named "old" 0.843
And I plug USB drive "old" 1.299
And I write an old version of the Tails USB image to disk "old" 1:2.738
When I start Tails from USB drive "old" with network unplugged 1:36.094
Then the boot device has safe access rights 3.670
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:305 3.816
After features/support/hooks.rb:89 0.011
Tags: @product
2:17.919
Before features/support/hooks.rb:259 0.008
Given a computer 0.337
And I start Tails from USB drive "old" with network unplugged and I login 1:29.440
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 35.389
And I take note of which tps features are available 2.896
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.666
After features/support/hooks.rb:305 0.233
After features/support/hooks.rb:89 0.012
Tags: @product
2:59.945
Before features/support/hooks.rb:259 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.294
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.196
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.463
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.856
After features/support/hooks.rb:305 0.154
After features/support/hooks.rb:89 0.010
Tags: @product
2:27.679
Before features/support/hooks.rb:259 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 10.577
And I log in to a new session 19.152
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.706
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.832
Then the running Tails is installed on USB drive "to_upgrade" 15.565
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:305 2.780
After features/support/hooks.rb:89 0.000
Tags: @product
2:25.874
Before features/support/hooks.rb:259 0.008
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.828
Then all tps features from the old Tails version are active 1.913
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.552
After features/support/hooks.rb:305 0.793
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:45.889
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.732
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.440
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.037
And Tor is ready 21.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.466
Given I shutdown Tails and wait for the computer to power off 8.827
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.343
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.351
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.301
When the network is plugged 0.050
And Tor is ready 18.097
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.054
Given I shutdown Tails and wait for the computer to power off 4.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.114
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.039
And Tor is ready 18.330
Then the Upgrader considers the system as up-to-date 0.346
# 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.664
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.020
After features/support/hooks.rb:305 0.727
After features/support/hooks.rb:89 0.025
Tags: @product @automatic_upgrade
37.578
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.867
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 18.201
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.385
After features/support/hooks.rb:305 0.632
After features/support/hooks.rb:89 0.000