Project Number Date
test_Tails_ISO_improve-cmd-logging 6 20 Jul 2025, 14:54

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 23:21.750 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:15.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 35.627
When I start Tails from USB drive "old" with network unplugged 1:32.529
Then the boot device has safe access rights 4.511
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.385
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 4.150
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:42.538
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 37.429
And I take note of which tps features are available 2.588
Then a Tails persistence partition exists on USB drive "old" 0.958
And I shutdown Tails and wait for the computer to power off 10.471
After features/support/hooks.rb:330 0.297
After features/support/hooks.rb:100 0.008
Tags: @product
3:37.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:55.720
Then Tails is running from USB drive "old" 0.888
And all tps features are active 3.085
When I write some files expected to persist 2.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.319
And all persistence configuration files have safe access rights 0.481
And all persistent directories from the old Tails version have safe access rights 2.580
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.748
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.873
After features/support/hooks.rb:330 0.321
After features/support/hooks.rb:100 0.021
Tags: @product
3:5.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.048
And I log in to a new session 21.397
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.118
And I plug USB drive "to_upgrade" 7.128
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.305
Then the running Tails is installed on USB drive "to_upgrade" 33.777
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 1.169
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:36.053
Then all tps features from the old Tails version are active 2.194
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.755
And the expected persistent files created with the old Tails version are present in the filesystem 1.816
And all persistent directories from the old Tails version have safe access rights 2.861
After features/support/hooks.rb:330 2.600
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
7:59.389
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.495
And no SquashFS delta is installed 1.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.557
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.274
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.694
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.688
When the network is plugged 0.110
And Tor is ready 23.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.066
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.754
Given I shutdown Tails and wait for the computer to power off 9.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.718
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.910
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
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.326
# 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.364
When the network is plugged 0.075
And Tor is ready 27.138
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.482
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.872
Given I shutdown Tails and wait for the computer to power off 7.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.690
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.852
And the file system changes introduced in version 6.3~testoverlayfs are present 0.730
And only the 6.3~testoverlayfs SquashFS delta is installed 0.176
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.350
And Tor is ready 21.218
Then the Upgrader considers the system as up-to-date 0.354
# 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 18.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 4.062
After features/support/hooks.rb:330 1.397
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
1:2.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.472
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.626
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.199
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 47.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.926
After features/support/hooks.rb:330 1.110
After features/support/hooks.rb:100 0.000