Project Number Date
test_Tails_ISO_stable 4760 01 Apr 2024, 11:54

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 17:15.187 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:47.407
Before features/support/hooks.rb:245 0.005
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.111
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 35.689
When I start Tails from USB drive "old" with network unplugged 1:6.580
Then the boot device has safe access rights 2.833
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 0.822
After features/support/hooks.rb:75 0.009
Tags: @product
2:2.222
Before features/support/hooks.rb:245 0.006
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login 1:17.057
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 34.505
And I take note of which tps features are available 1.182
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.473
Before features/support/hooks.rb:245 0.006
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.649
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.866
When I write some files expected to persist 1.578
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.736
And I take note of which tps features are available 0.354
And I shutdown Tails and wait for the computer to power off 4.482
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.704
After features/support/hooks.rb:291 0.139
After features/support/hooks.rb:75 0.008
Tags: @product
2:16.859
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 9.656
And I log in to a new session 14.443
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.478
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.688
Then the running Tails is installed on USB drive "to_upgrade" 12.839
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:291 1.101
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.799
Before features/support/hooks.rb:245 0.005
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.344
Then all tps features from the old Tails version are active 1.288
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.884
And the expected persistent files created with the old Tails version are present in the filesystem 1.510
And all persistent directories from the old Tails version have safe access rights 2.305
After features/support/hooks.rb:291 0.735
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
6:18.435
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.124
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.034
And Tor is ready 16.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.021
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.081
Given I shutdown Tails and wait for the computer to power off 6.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.419
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.304
When the network is plugged 0.042
And Tor is ready 46.265
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.455
Given I shutdown Tails and wait for the computer to power off 4.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.768
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.700
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.336
When the network is plugged 0.030
And Tor is ready 15.136
Then the Upgrader considers the system as up-to-date 0.313
# 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.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.983
After features/support/hooks.rb:291 1.015
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
31.990
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 10.362
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.047
And the signing key used by the Upgrader is outdated 0.575
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 15.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.082
After features/support/hooks.rb:291 0.612
After features/support/hooks.rb:75 0.000