Project Number Date
test_Tails_ISO_stable 4717 13 Mar 2024, 20:52

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:38.095 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:42.586
Before features/support/hooks.rb:245 0.006
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 19.994
When I start Tails from USB drive "old" with network unplugged 1:17.547
Then the boot device has safe access rights 2.899
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:291 3.531
After features/support/hooks.rb:75 0.010
Tags: @product
2:4.892
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:12.495
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 41.290
And I take note of which tps features are available 1.815
Then a Tails persistence partition exists on USB drive "old" 0.742
And I shutdown Tails and wait for the computer to power off 8.035
After features/support/hooks.rb:291 0.146
After features/support/hooks.rb:75 0.010
Tags: @product
2:27.045
Before features/support/hooks.rb:245 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:1.707
Then Tails is running from USB drive "old" 0.382
And all tps features are active 1.754
When I write some files expected to persist 1.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 3.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.936
After features/support/hooks.rb:291 0.177
After features/support/hooks.rb:75 0.010
Tags: @product
2:31.213
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.163
And I log in to a new session 16.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.669
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.741
Then the running Tails is installed on USB drive "to_upgrade" 12.662
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:291 3.535
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.170
Before features/support/hooks.rb:245 0.007
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.309
Then all tps features from the old Tails version are active 1.495
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 2.932
And the expected persistent files created with the old Tails version are present in the filesystem 1.469
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:23.280
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.436
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.031
And Tor is ready 18.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.333
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.351
Given I shutdown Tails and wait for the computer to power off 6.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.865
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.718
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.261
When the network is plugged 0.032
And Tor is ready 43.755
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.200
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 1:55.637
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.734
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.047
And Tor is ready 14.273
Then the Upgrader considers the system as up-to-date 10.633
# 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.402
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.828
After features/support/hooks.rb:291 0.828
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
31.905
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.873
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.533
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.140
After features/support/hooks.rb:291 0.639
After features/support/hooks.rb:75 0.000