Project Number Date
test_Tails_ISO_stable 5179 13 Oct 2024, 08:48

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 19:4.784 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:31.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 59.255
When I start Tails from USB drive "old" with network unplugged 1:27.230
Then the boot device has safe access rights 3.063
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.524
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.483
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:20.619
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 31.759
And I take note of which tps features are available 1.448
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 8.346
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.217
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.779
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.165
When I write some files expected to persist 1.677
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.457
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.171
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.786
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 11.320
And I log in to a new session 20.472
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.614
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.274
Then the running Tails is installed on USB drive "to_upgrade" 20.872
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.487
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.670
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.575
And all persistent directories from the old Tails version have safe access rights 2.503
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:22.947
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.889
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.477
When the network is plugged 0.089
And Tor is ready 23.672
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.313
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.559
Given I shutdown Tails and wait for the computer to power off 8.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.598
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.271
When the network is plugged 0.066
And Tor is ready 19.569
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.954
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.116
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.645
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.571
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.092
And Tor is ready 20.678
Then the Upgrader considers the system as up-to-date 0.307
# 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 13.893
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.979
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.010
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.885
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.513
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000