Project Number Date
test_Tails_ISO_devel 3893 01 Jul 2025, 13:50

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:48.406 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:23.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.721
When I start Tails from USB drive "old" with network unplugged 1:44.714
Then the boot device has safe access rights 3.450
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 7.275
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:34.858
Then Tails is running from USB drive "old" 0.931
And I create a persistent partition 37.716
And I take note of which tps features are available 3.198
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.961
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
3:17.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.689
Then Tails is running from USB drive "old" 1.639
And all tps features are active 2.681
When I write some files expected to persist 3.330
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.347
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.572
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 6.882
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.780
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.012
Tags: @product
2:49.583
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 9.669
And I log in to a new session 24.299
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.238
And I plug USB drive "to_upgrade" 2.553
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.439
Then the running Tails is installed on USB drive "to_upgrade" 29.990
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 4.652
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.281
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.451
Then all tps features from the old Tails version are active 2.785
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.503
And all persistent directories from the old Tails version have safe access rights 2.913
After features/support/hooks.rb:330 1.348
After features/support/hooks.rb:100 0.018
7:17.327
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 14.524
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.466
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.592
When the network is plugged 0.166
And Tor is ready 21.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.711
Given I shutdown Tails and wait for the computer to power off 11.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.543
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.857
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.339
When the network is plugged 0.076
And Tor is ready 21.295
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.715
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.571
Given I shutdown Tails and wait for the computer to power off 4.667
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.401
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.142
And Tor is ready 21.570
Then the Upgrader considers the system as up-to-date 0.302
# 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.365
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.788
After features/support/hooks.rb:330 0.920
After features/support/hooks.rb:100 0.102
1:0.593
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.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 47.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
After features/support/hooks.rb:330 0.774
After features/support/hooks.rb:100 0.000