Project Number Date
test_Tails_ISO_stable 5673 24 May 2025, 13:14

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:14.798 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:25.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 35.279
When I start Tails from USB drive "old" with network unplugged 1:44.452
Then the boot device has safe access rights 3.352
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 11.775
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.587
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:43.242
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 37.875
And I take note of which tps features are available 1.921
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 9.106
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.012
Tags: @product
3:13.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.126
Then Tails is running from USB drive "old" 0.530
And all tps features are active 2.151
When I write some files expected to persist 2.603
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.973
And I take note of which tps features are available 0.565
And I shutdown Tails and wait for the computer to power off 4.635
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.531
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.959
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 11.286
And I log in to a new session 20.401
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.002
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.168
Then the running Tails is installed on USB drive "to_upgrade" 26.155
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 2.297
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.935
Then all tps features from the old Tails version are active 2.617
And Tails is running from USB drive "to_upgrade" 0.456
And the boot device has safe access rights 3.684
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.888
After features/support/hooks.rb:330 1.305
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
7:19.062
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 28.064
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.583
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.446
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.590
When the network is plugged 0.087
And Tor is ready 22.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.151
Given I shutdown Tails and wait for the computer to power off 11.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.126
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.655
And the file system changes introduced in version 6.2~testoverlayfs are present 0.452
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.456
# 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.341
When the network is plugged 0.076
And Tor is ready 19.194
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.983
Given I shutdown Tails and wait for the computer to power off 4.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.348
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.039
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.078
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.114
And Tor is ready 20.614
Then the Upgrader considers the system as up-to-date 0.344
# 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 17.005
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.574
After features/support/hooks.rb:330 0.872
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
38.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.688
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.603
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.145
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 19.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.507
After features/support/hooks.rb:330 1.742
After features/support/hooks.rb:100 0.000