Project Number Date
test_Tails_ISO_stable 5571 13 Apr 2025, 13: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:21.805 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:11.423
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.246
When I start Tails from USB drive "old" with network unplugged 1:34.716
Then the boot device has safe access rights 3.129
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 6.956
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:33.091
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 32.781
And I take note of which tps features are available 1.847
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.688
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.110
Then Tails is running from USB drive "old" 1.559
And all tps features are active 2.074
When I write some files expected to persist 2.341
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.430
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 7.015
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.728
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.832
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 10.454
And I log in to a new session 21.138
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.882
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.286
Then the running Tails is installed on USB drive "to_upgrade" 27.273
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.030
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.886
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 3.206
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:330 1.361
After features/support/hooks.rb:100 0.014
6:54.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.696
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.060
And Tor is ready 21.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.716
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.426
Given I shutdown Tails and wait for the computer to power off 8.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.223
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.261
When the network is plugged 0.080
And Tor is ready 18.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.976
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.361
Given I shutdown Tails and wait for the computer to power off 4.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.549
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.062
And Tor is ready 19.330
Then the Upgrader considers the system as up-to-date 0.330
# 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.496
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.680
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.014
59.209
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 11.004
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 47.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.617
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.000