Project Number Date
test_Tails_ISO_stable 5642 12 May 2025, 14:33

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:2.963 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:5.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.049
When I start Tails from USB drive "old" with network unplugged 1:28.812
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 7.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.532
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:27.588
Then Tails is running from USB drive "old" 0.414
And I create a persistent partition 34.485
And I take note of which tps features are available 1.591
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.489
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.025
Tags: @product
2:54.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.697
Then Tails is running from USB drive "old" 0.394
And all tps features are active 2.062
When I write some files expected to persist 1.871
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 3.241
And I take note of which tps features are available 0.861
And I shutdown Tails and wait for the computer to power off 4.398
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.331
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.626
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 without a persistent partition and stopped at Tails Greeter's login screen 10.891
And I log in to a new session 19.719
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.151
And I plug USB drive "to_upgrade" 2.603
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.116
Then the running Tails is installed on USB drive "to_upgrade" 21.700
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 3.529
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.641
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.663
Then all tps features from the old Tails version are active 1.719
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.490
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.575
After features/support/hooks.rb:330 1.297
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:13.397
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 with a persistent partition enabled and logged in 12.366
And no SquashFS delta is installed 0.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.732
When the network is plugged 0.062
And Tor is ready 19.999
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.074
Given I shutdown Tails and wait for the computer to power off 8.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.203
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.418
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.403
When the network is plugged 0.086
And Tor is ready 15.607
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.054
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.108
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.899
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 3.258
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.059
And Tor is ready 49.094
Then the Upgrader considers the system as up-to-date 0.309
# 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.245
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.758
After features/support/hooks.rb:330 0.780
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.800
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 9.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 20.257
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.143
After features/support/hooks.rb:330 0.820
After features/support/hooks.rb:100 0.000