Project Number Date
test_Tails_ISO_stable 5462 17 Feb 2025, 08:49

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:30.208 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:55.934
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.738
When I start Tails from USB drive "old" with network unplugged 1:21.815
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.043
Tags: @product
2:7.168
Before features/support/hooks.rb:269 0.005
Given a computer 0.278
And I start Tails from USB drive "old" with network unplugged and I login 1:24.122
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.773
And I take note of which tps features are available 1.456
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.391
After features/support/hooks.rb:326 0.230
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.345
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.054
Then Tails is running from USB drive "old" 0.510
And all tps features are active 2.079
When I write some files expected to persist 1.748
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.770
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.283
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.561
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.053
Before features/support/hooks.rb:269 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.012
And I log in to a new session 18.462
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.384
Then the running Tails is installed on USB drive "to_upgrade" 18.817
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 6.649
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.467
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.272
Then all tps features from the old Tails version are active 1.783
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 4.062
And the expected persistent files created with the old Tails version are present in the filesystem 1.327
And all persistent directories from the old Tails version have safe access rights 2.465
After features/support/hooks.rb:326 0.629
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:18.481
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.115
And no SquashFS delta is installed 0.187
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.070
And Tor is ready 19.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.018
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.227
Given I shutdown Tails and wait for the computer to power off 8.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.608
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.567
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.329
When the network is plugged 0.085
And Tor is ready 17.777
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.551
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.225
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.614
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.078
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.074
And Tor is ready 20.493
Then the Upgrader considers the system as up-to-date 0.308
# 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.405
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.005
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.757
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.354
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.000