Project Number Date
test_Tails_ISO_devel 4116 11 Dec 2025, 23:30

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 15:49.143 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
1:54.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 40.642
When I start Tails from USB drive "old" with network unplugged 1:7.758
Then the boot device has safe access rights 3.986
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:331 3.768
After features/support/hooks.rb:100 0.009
Tags: @product
1:53.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:11.523
Then Tails is running from USB drive "old" 0.730
And I create a persistent partition 29.551
And I take note of which tps features are available 1.271
Then a Tails persistence partition exists on USB drive "old" 0.738
And I shutdown Tails and wait for the computer to power off 9.257
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.011
Tags: @product
2:0.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 2.889
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.674
Then Tails is running from USB drive "old" 0.337
And all tps features are active 2.105
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 3.184
And I take note of which tps features are available 0.608
And I shutdown Tails and wait for the computer to power off 7.950
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.005
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.007
Tags: @product
2:40.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.790
And I log in to a new session 19.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.612
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.689
Then the running Tails is installed on USB drive "to_upgrade" 22.187
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.285
After features/support/hooks.rb:331 4.144
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.712
Then all tps features from the old Tails version are active 1.500
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.401
And the expected persistent files created with the old Tails version are present in the filesystem 1.788
And all persistent directories from the old Tails version have safe access rights 3.610
After features/support/hooks.rb:331 1.509
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:25.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.869
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.081
And Tor is ready 14.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.712
Given I shutdown Tails and wait for the computer to power off 16.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.550
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.627
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.240
When the network is plugged 0.062
And Tor is ready 12.118
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.646
Given I shutdown Tails and wait for the computer to power off 4.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.626
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.648
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.228
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.397
When the network is plugged 0.108
And Tor is ready 42.204
Then the Upgrader considers the system as up-to-date 0.128
# 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 6.082
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.498
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
25.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 12.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.785
After features/support/hooks.rb:331 0.860
After features/support/hooks.rb:100 0.000