Project Number Date
test_Tails_ISO_stable 4851 23 May 2024, 14:03

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 20:54.167 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:12.885
Before features/support/hooks.rb:259 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 33.671
When I start Tails from USB drive "old" with network unplugged 1:33.285
Then the boot device has safe access rights 3.469
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:305 7.275
After features/support/hooks.rb:89 0.012
Tags: @product
2:24.110
Before features/support/hooks.rb:259 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:34.524
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 38.252
And I take note of which tps features are available 1.547
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:305 0.150
After features/support/hooks.rb:89 0.012
Tags: @product
2:59.143
Before features/support/hooks.rb:259 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.336
Then Tails is running from USB drive "old" 0.444
And all tps features are active 2.220
When I write some files expected to persist 1.950
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.576
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.520
And I shutdown Tails and wait for the computer to power off 4.155
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.666
After features/support/hooks.rb:305 0.121
After features/support/hooks.rb:89 0.011
Tags: @product
2:27.759
Before features/support/hooks.rb:259 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 11.390
And I log in to a new session 17.762
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.590
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.884
Then the running Tails is installed on USB drive "to_upgrade" 19.273
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:305 3.120
After features/support/hooks.rb:89 0.000
Tags: @product
2:28.381
Before features/support/hooks.rb:259 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.803
Then all tps features from the old Tails version are active 1.721
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.337
And the expected persistent files created with the old Tails version are present in the filesystem 1.472
And all persistent directories from the old Tails version have safe access rights 2.520
After features/support/hooks.rb:305 0.636
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
7:41.327
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.676
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
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.468
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.047
And Tor is ready 20.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.441
Given I shutdown Tails and wait for the computer to power off 1:14.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.982
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.426
# 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.262
When the network is plugged 0.056
And Tor is ready 19.941
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.962
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.585
Given I shutdown Tails and wait for the computer to power off 4.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.014
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.434
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.034
And Tor is ready 20.327
Then the Upgrader considers the system as up-to-date 0.315
# 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.482
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.954
After features/support/hooks.rb:305 0.818
After features/support/hooks.rb:89 0.038
Tags: @product @automatic_upgrade
40.559
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.718
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 19.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.110
After features/support/hooks.rb:305 1.273
After features/support/hooks.rb:89 0.000