Project Number Date
test_Tails_ISO_devel 3807 13 May 2025, 09: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 19:58.428 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:12.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 30.506
When I start Tails from USB drive "old" with network unplugged 1:35.668
Then the boot device has safe access rights 3.467
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.749
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.534
And I start Tails from USB drive "old" with network unplugged and I login 1:30.245
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 31.851
And I take note of which tps features are available 2.230
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.373
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.021
Tags: @product
3:0.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.838
Then Tails is running from USB drive "old" 1.309
And all tps features are active 2.091
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 4.703
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 6.590
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.996
After features/support/hooks.rb:330 0.135
After features/support/hooks.rb:100 0.011
Tags: @product
2:49.244
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.768
And I log in to a new session 20.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.625
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.393
Then the running Tails is installed on USB drive "to_upgrade" 31.219
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.110
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.390
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:330 1.225
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
6:42.424
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 with a persistent partition enabled and logged in 12.411
And no SquashFS delta is installed 0.210
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
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.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.075
And Tor is ready 24.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.086
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.152
Given I shutdown Tails and wait for the computer to power off 11.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.870
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.153
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.421
When the network is plugged 0.078
And Tor is ready 19.630
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.235
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.917
Given I shutdown Tails and wait for the computer to power off 4.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.864
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.144
# 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.467
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.084
And Tor is ready 20.523
Then the Upgrader considers the system as up-to-date 0.345
# 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.686
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.608
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.340
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 with a persistent partition enabled and logged in 10.618
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.088
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.089
After features/support/hooks.rb:330 0.877
After features/support/hooks.rb:100 0.000