Project Number Date
test_Tails_ISO_stable 5550 03 Apr 2025, 15:03

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:12.070 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:40.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.316
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 40.882
When I start Tails from USB drive "old" with network unplugged 1:53.279
Then the boot device has safe access rights 3.418
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 10.428
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:30.550
Then Tails is running from USB drive "old" 0.430
And I create a persistent partition 33.002
And I take note of which tps features are available 1.651
Then a Tails persistence partition exists on USB drive "old" 0.997
And I shutdown Tails and wait for the computer to power off 9.006
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.020
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.019
Then Tails is running from USB drive "old" 0.666
And all tps features are active 2.111
When I write some files expected to persist 2.174
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.755
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 6.521
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.317
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.927
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 9.702
And I log in to a new session 19.846
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.792
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.534
Then the running Tails is installed on USB drive "to_upgrade" 26.059
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.268
After features/support/hooks.rb:330 2.759
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.161
Then all tps features from the old Tails version are active 2.122
And Tails is running from USB drive "to_upgrade" 0.408
And the boot device has safe access rights 3.655
And the expected persistent files created with the old Tails version are present in the filesystem 2.008
And all persistent directories from the old Tails version have safe access rights 2.668
After features/support/hooks.rb:330 1.339
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:30.054
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 14.733
And no SquashFS delta is installed 0.177
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.545
When the network is plugged 0.072
And Tor is ready 28.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.610
Given I shutdown Tails and wait for the computer to power off 11.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.888
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.355
When the network is plugged 0.102
And Tor is ready 45.931
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.616
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.081
Given I shutdown Tails and wait for the computer to power off 4.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.645
Then Tails is running version 6.3~testoverlayfs 0.057
And all tps features are active 2.210
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.091
And Tor is ready 19.599
Then the Upgrader considers the system as up-to-date 0.324
# 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 16.839
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.874
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
42.754
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 12.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 22.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.242
After features/support/hooks.rb:330 1.748
After features/support/hooks.rb:100 0.000