Project Number Date
test_Tails_ISO_20979-pdfarranger 7 02 Jun 2025, 02: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 19:44.149 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:19.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.446
When I start Tails from USB drive "old" with network unplugged 1:41.884
Then the boot device has safe access rights 3.514
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 7.096
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:25.657
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 30.277
And I take note of which tps features are available 2.173
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.784
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.007
Tags: @product
2:54.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.436
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.067
When I write some files expected to persist 1.781
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.601
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 6.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.315
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.551
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.125
And I log in to a new session 18.639
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.484
And I plug USB drive "to_upgrade" 2.609
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.097
Then the running Tails is installed on USB drive "to_upgrade" 22.138
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 6.645
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.627
Then all tps features from the old Tails version are active 1.663
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.530
After features/support/hooks.rb:330 1.664
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:47.368
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 12.124
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.469
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.126
And Tor is ready 18.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.759
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.716
Given I shutdown Tails and wait for the computer to power off 8.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.091
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.404
# 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.343
When the network is plugged 0.070
And Tor is ready 19.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.562
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.422
Given I shutdown Tails and wait for the computer to power off 6.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.005
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.066
And Tor is ready 17.770
Then the Upgrader considers the system as up-to-date 10.813
# 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.836
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.525
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.088
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 10.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.740
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.145
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.146
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.698
After features/support/hooks.rb:330 0.739
After features/support/hooks.rb:100 0.000