Project Number Date
test_Tails_ISO_stable 5557 06 Apr 2025, 09:10

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:33.441 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:17.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.117
When I start Tails from USB drive "old" with network unplugged 1:40.931
Then the boot device has safe access rights 3.108
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:330 3.705
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.900
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:30.145
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 32.999
And I take note of which tps features are available 2.057
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.336
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.883
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.990
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.122
When I write some files expected to persist 1.838
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.683
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.381
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.245
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.007
Tags: @product
2:26.898
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.231
And I log in to a new session 18.179
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.489
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.950
Then the running Tails is installed on USB drive "to_upgrade" 20.166
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 3.002
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.288
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.347
After features/support/hooks.rb:330 1.071
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:43.647
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 12.042
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.018
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.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.067
And Tor is ready 22.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.054
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.370
Given I shutdown Tails and wait for the computer to power off 1:26.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.266
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.080
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.398
# 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.252
When the network is plugged 0.074
And Tor is ready 16.189
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.487
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.746
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.087
And Tor is ready 17.831
Then the Upgrader considers the system as up-to-date 0.307
# 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.669
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.648
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.588
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.253
And the signing key used by the Upgrader is outdated 0.147
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 20.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.801
After features/support/hooks.rb:330 0.672
After features/support/hooks.rb:100 0.000