Project Number Date
test_Tails_ISO_stable 5316 06 Dec 2024, 09:01

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 21:10.684 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:15.834
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.562
When I start Tails from USB drive "old" with network unplugged 1:40.037
Then the boot device has safe access rights 2.987
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.569
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.747
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:25.760
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 32.653
And I take note of which tps features are available 1.536
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.347
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.017
Tags: @product
2:59.747
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.236
Then Tails is running from USB drive "old" 1.149
And all tps features are active 2.279
When I write some files expected to persist 2.154
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.605
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:39.557
Before features/support/hooks.rb:269 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 12.928
And I log in to a new session 21.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.062
Then the running Tails is installed on USB drive "to_upgrade" 24.034
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.543
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.077
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.864
Then all tps features from the old Tails version are active 1.642
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 4.120
And the expected persistent files created with the old Tails version are present in the filesystem 1.556
And all persistent directories from the old Tails version have safe access rights 2.405
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:7.947
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.486
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.500
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.429
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.077
And Tor is ready 23.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.707
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.592
Given I shutdown Tails and wait for the computer to power off 1:20.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.924
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.426
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.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.358
When the network is plugged 0.082
And Tor is ready 19.403
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.761
Given I shutdown Tails and wait for the computer to power off 4.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.428
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.027
And the file system changes introduced in version 6.3~testoverlayfs are present 0.717
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.360
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.066
And Tor is ready 18.971
Then the Upgrader considers the system as up-to-date 10.841
# 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.320
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 1.106
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.772
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.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.818
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.394
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000