Project Number Date
test_Tails_ISO_stable 5714 13 Jun 2025, 14:37

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 28:6.024 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
3:3.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 52.107
When I start Tails from USB drive "old" with network unplugged 2:5.179
Then the boot device has safe access rights 3.472
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.412
And I unplug USB drive "old" 0.365
After features/support/hooks.rb:330 3.915
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.802
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 2:17.418
Then Tails is running from USB drive "old" 0.523
And I create a persistent partition 42.228
And I take note of which tps features are available 4.731
Then a Tails persistence partition exists on USB drive "old" 3.172
And I shutdown Tails and wait for the computer to power off 9.519
After features/support/hooks.rb:330 0.218
After features/support/hooks.rb:100 0.019
Tags: @product
4:1.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:9.363
Then Tails is running from USB drive "old" 0.933
And all tps features are active 3.207
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 3.027
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 10.683
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.342
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
3:35.109
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 without a persistent partition and stopped at Tails Greeter's login screen 15.490
And I log in to a new session 28.366
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.720
And I plug USB drive "to_upgrade" 2.577
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:6.794
Then the running Tails is installed on USB drive "to_upgrade" 34.726
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 4.639
After features/support/hooks.rb:100 0.000
Tags: @product
3:28.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 1.361
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:8.221
Then all tps features from the old Tails version are active 2.456
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.638
And the expected persistent files created with the old Tails version are present in the filesystem 2.224
And all persistent directories from the old Tails version have safe access rights 9.788
After features/support/hooks.rb:330 3.354
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
9:42.986
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 17.135
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.752
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.299
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.873
When the network is plugged 0.092
And Tor is ready 58.934
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.066
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.694
Given I shutdown Tails and wait for the computer to power off 13.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.966
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.741
And the file system changes introduced in version 6.2~testoverlayfs are present 0.382
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.363
When the network is plugged 0.076
And Tor is ready 30.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.531
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.737
Given I shutdown Tails and wait for the computer to power off 7.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:55.250
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.313
And the file system changes introduced in version 6.3~testoverlayfs are present 1.355
And only the 6.3~testoverlayfs SquashFS delta is installed 1.186
# 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.838
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.705
When the network is plugged 0.237
And Tor is ready 26.907
Then the Upgrader considers the system as up-to-date 0.391
# 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 21.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.671
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
56.805
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 17.490
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 26.755
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.930
After features/support/hooks.rb:330 1.794
After features/support/hooks.rb:100 0.000