Project Number Date
test_Tails_ISO_stable 4707 11 Mar 2024, 14:19

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:45.914 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:35.198
Before features/support/hooks.rb:245 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 19.968
When I start Tails from USB drive "old" with network unplugged 1:9.786
Then the boot device has safe access rights 3.116
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:291 3.577
After features/support/hooks.rb:75 0.009
Tags: @product
2:10.987
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:17.482
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 42.419
And I take note of which tps features are available 1.728
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.038
After features/support/hooks.rb:291 0.176
After features/support/hooks.rb:75 0.009
Tags: @product
2:44.012
Before features/support/hooks.rb:245 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.976
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.143
When I write some files expected to persist 1.675
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.404
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 3.067
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.100
After features/support/hooks.rb:291 0.125
After features/support/hooks.rb:75 0.008
Tags: @product
2:31.951
Before features/support/hooks.rb:245 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.546
And I log in to a new session 18.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.299
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.173
Then the running Tails is installed on USB drive "to_upgrade" 12.997
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 6.696
After features/support/hooks.rb:75 0.000
Tags: @product
2:22.216
Before features/support/hooks.rb:245 0.007
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.053
Then all tps features from the old Tails version are active 1.545
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 3.151
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.411
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:47.352
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.431
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.041
And Tor is ready 21.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.087
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.932
Given I shutdown Tails and wait for the computer to power off 7.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.889
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.993
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.242
When the network is plugged 0.040
And Tor is ready 17.861
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.812
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.037
Given I shutdown Tails and wait for the computer to power off 4.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.653
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.877
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.058
And Tor is ready 18.759
Then the Upgrader considers the system as up-to-date 0.252
# 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.605
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.011
After features/support/hooks.rb:291 0.756
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
34.194
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.719
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 15.129
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.872
After features/support/hooks.rb:291 0.719
After features/support/hooks.rb:75 0.000