Project Number Date
test_Tails_ISO_stable 5560 09 Apr 2025, 09: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 21:11.730 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.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.613
When I start Tails from USB drive "old" with network unplugged 1:32.739
Then the boot device has safe access rights 3.223
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 3.762
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.297
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:29.290
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.680
And I take note of which tps features are available 1.818
Then a Tails persistence partition exists on USB drive "old" 0.714
And I shutdown Tails and wait for the computer to power off 8.262
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.993
Then Tails is running from USB drive "old" 0.337
And all tps features are active 2.135
When I write some files expected to persist 1.850
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.595
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.148
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.979
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 9.844
And I log in to a new session 17.996
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.351
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.405
Then the running Tails is installed on USB drive "to_upgrade" 28.468
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 6.716
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.277
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:6.675
Then all tps features from the old Tails version are active 1.585
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.487
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.420
After features/support/hooks.rb:330 1.190
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:23.208
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 25.557
And no SquashFS delta is installed 0.177
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.107
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.070
And Tor is ready 23.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.955
Given I shutdown Tails and wait for the computer to power off 1:26.069
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.232
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.198
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.280
When the network is plugged 0.065
And Tor is ready 18.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.824
Given I shutdown Tails and wait for the computer to power off 4.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.830
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.295
When the network is plugged 0.068
And Tor is ready 20.071
Then the Upgrader considers the system as up-to-date 0.315
# 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.300
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.789
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.287
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 9.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.384
After features/support/hooks.rb:330 0.805
After features/support/hooks.rb:100 0.000