Project Number Date
test_Tails_ISO_20872-more-gtk-launch 7 02 Apr 2025, 08:20

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 18:58.093 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
1:56.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.228
When I start Tails from USB drive "old" with network unplugged 1:21.781
Then the boot device has safe access rights 2.860
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 6.746
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:27.323
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 31.946
And I take note of which tps features are available 1.446
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.616
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 "old" with network unplugged and I login with persistence enabled 2:10.621
Then Tails is running from USB drive "old" 1.579
And all tps features are active 2.076
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.379
And I take note of which tps features are available 0.865
And I shutdown Tails and wait for the computer to power off 6.154
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.517
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.682
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.724
And I log in to a new session 18.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.505
Then the running Tails is installed on USB drive "to_upgrade" 24.111
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 7.240
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.352
Then all tps features from the old Tails version are active 1.700
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.282
After features/support/hooks.rb:330 1.177
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.681
And no SquashFS delta is installed 0.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.232
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.081
And Tor is ready 20.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.361
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.813
Given I shutdown Tails and wait for the computer to power off 8.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.056
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.453
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.307
When the network is plugged 0.060
And Tor is ready 20.341
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.247
Given I shutdown Tails and wait for the computer to power off 4.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.049
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.018
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.066
And Tor is ready 19.304
Then the Upgrader considers the system as up-to-date 0.322
# 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.573
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.631
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.098
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 9.819
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.555
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 20.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
After features/support/hooks.rb:330 0.652
After features/support/hooks.rb:100 0.000