Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 25 01 Apr 2025, 02:44

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 19:0.498 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:55.427
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.669
When I start Tails from USB drive "old" with network unplugged 1:21.312
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 6.813
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:21.611
Then Tails is running from USB drive "old" 0.285
And I create a persistent partition 30.982
And I take note of which tps features are available 1.479
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 6.353
After features/support/hooks.rb:330 0.103
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.676
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.491
Then Tails is running from USB drive "old" 0.701
And all tps features are active 1.883
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.217
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.504
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.351
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.828
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.649
And I log in to a new session 21.251
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.329
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.427
Then the running Tails is installed on USB drive "to_upgrade" 19.164
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 2.779
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.237
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.093
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 2.293
After features/support/hooks.rb:330 1.557
After features/support/hooks.rb:100 0.008
6:46.114
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.692
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.061
And Tor is ready 18.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.282
Given I shutdown Tails and wait for the computer to power off 8.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.870
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.061
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.241
# 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.237
When the network is plugged 0.078
And Tor is ready 46.912
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.574
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.327
Given I shutdown Tails and wait for the computer to power off 4.669
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.662
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.083
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
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.263
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.100
And Tor is ready 19.187
Then the Upgrader considers the system as up-to-date 0.402
# 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.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.004
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.016
34.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 23.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.845
After features/support/hooks.rb:330 1.054
After features/support/hooks.rb:100 0.000