Project Number Date
test_Tails_ISO_stable 4864 31 May 2024, 19:13

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:54.427 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:7.178
Before features/support/hooks.rb:265 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.697
When I start Tails from USB drive "old" with network unplugged 1:30.291
Then the boot device has safe access rights 2.967
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:311 3.477
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.177
Before features/support/hooks.rb:265 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:25.463
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 37.163
And I take note of which tps features are available 1.812
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.255
After features/support/hooks.rb:311 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.023
Before features/support/hooks.rb:265 0.006
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.857
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.189
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 2.562
And I take note of which tps features are available 0.519
And I shutdown Tails and wait for the computer to power off 4.398
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.459
After features/support/hooks.rb:311 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.549
Before features/support/hooks.rb:265 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 12.530
And I log in to a new session 18.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.693
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.433
Then the running Tails is installed on USB drive "to_upgrade" 17.329
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:311 1.990
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.486
Before features/support/hooks.rb:265 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.703
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.636
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:311 0.690
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:25.340
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.895
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.428
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.558
When the network is plugged 0.040
And Tor is ready 19.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.493
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.714
Given I shutdown Tails and wait for the computer to power off 8.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.437
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.277
When the network is plugged 0.039
And Tor is ready 19.951
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.100
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.407
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.178
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.030
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.085
# 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.281
When the network is plugged 0.037
And Tor is ready 17.275
Then the Upgrader considers the system as up-to-date 0.326
# 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.947
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.852
After features/support/hooks.rb:311 0.806
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.670
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.343
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
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 1.195
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 18.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.199
After features/support/hooks.rb:311 0.944
After features/support/hooks.rb:100 0.000