Project Number Date
test_Tails_ISO_stable 5605 28 Apr 2025, 20:46

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 21:26.785 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:41.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 55.649
When I start Tails from USB drive "old" with network unplugged 1:40.183
Then the boot device has safe access rights 3.217
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 7.056
After features/support/hooks.rb:100 0.048
Tags: @product
2:19.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login 1:34.233
Then Tails is running from USB drive "old" 0.425
And I create a persistent partition 32.530
And I take note of which tps features are available 2.101
Then a Tails persistence partition exists on USB drive "old" 0.945
And I shutdown Tails and wait for the computer to power off 8.827
After features/support/hooks.rb:330 0.230
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.630
Then Tails is running from USB drive "old" 0.465
And all tps features are active 2.157
When I write some files expected to persist 2.158
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.858
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 6.330
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.345
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.051
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.814
And I log in to a new session 24.752
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.975
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.361
Then the running Tails is installed on USB drive "to_upgrade" 29.218
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 3.193
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.291
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.030
Then all tps features from the old Tails version are active 1.826
And Tails is running from USB drive "to_upgrade" 0.462
And the boot device has safe access rights 3.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.615
And all persistent directories from the old Tails version have safe access rights 2.693
After features/support/hooks.rb:330 1.656
After features/support/hooks.rb:100 0.012
7:17.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.517
And no SquashFS delta is installed 0.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.547
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.631
When the network is plugged 0.080
And Tor is ready 23.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.991
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.363
Given I shutdown Tails and wait for the computer to power off 11.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.579
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.387
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.529
# 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.284
When the network is plugged 0.131
And Tor is ready 18.961
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.509
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.692
Given I shutdown Tails and wait for the computer to power off 6.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.065
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.403
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.460
When the network is plugged 0.078
And Tor is ready 30.567
Then the Upgrader considers the system as up-to-date 0.334
# 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 16.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.549
After features/support/hooks.rb:330 0.865
After features/support/hooks.rb:100 0.023
42.446
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.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.675
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.129
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 23.578
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.016
After features/support/hooks.rb:330 1.056
After features/support/hooks.rb:100 0.000