Project Number Date
test_Tails_ISO_stable 5514 14 Mar 2025, 09:27

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:12.280 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:10.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.485
When I start Tails from USB drive "old" with network unplugged 1:35.708
Then the boot device has safe access rights 3.153
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:330 3.518
After features/support/hooks.rb:100 0.044
Tags: @product
2:13.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:29.947
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 32.156
And I take note of which tps features are available 1.553
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.023
Then Tails is running from USB drive "old" 0.342
And all tps features are active 2.198
When I write some files expected to persist 1.881
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.352
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 2.909
And I take note of which tps features are available 0.599
And I shutdown Tails and wait for the computer to power off 4.526
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.136
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.920
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 without a persistent partition and stopped at Tails Greeter's login screen 10.994
And I log in to a new session 20.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.689
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.229
Then the running Tails is installed on USB drive "to_upgrade" 21.118
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.255
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.774
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.193
Then all tps features from the old Tails version are active 1.941
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.119
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:330 1.060
After features/support/hooks.rb:100 0.007
7:3.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.094
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.196
And Tor is ready 24.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.341
Given I shutdown Tails and wait for the computer to power off 11.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.618
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.351
When the network is plugged 0.095
And Tor is ready 16.538
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.613
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.294
Given I shutdown Tails and wait for the computer to power off 6.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.776
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.069
And Tor is ready 21.381
Then the Upgrader considers the system as up-to-date 0.366
# 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.597
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.017
42.390
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.563
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 27.392
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.794
After features/support/hooks.rb:330 0.668
After features/support/hooks.rb:100 0.000