Project Number Date
test_Tails_ISO_stable 5753 01 Jul 2025, 13:09

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 25:2.589 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:42.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.305
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 42.147
When I start Tails from USB drive "old" with network unplugged 1:47.676
Then the boot device has safe access rights 8.369
And Tails is running from USB drive "old" 0.832
And there is no persistence partition on USB drive "old" 0.111
And process "udev-watchdog" is running 0.150
And udev-watchdog is monitoring the correct device 0.884
And I unplug USB drive "old" 0.585
After features/support/hooks.rb:330 4.084
After features/support/hooks.rb:100 0.006
Tags: @product
2:54.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:57.747
Then Tails is running from USB drive "old" 0.653
And I create a persistent partition 42.240
And I take note of which tps features are available 2.366
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 10.533
After features/support/hooks.rb:330 0.482
After features/support/hooks.rb:100 0.006
Tags: @product
3:59.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.880
Then Tails is running from USB drive "old" 0.731
And all tps features are active 2.148
When I write some files expected to persist 2.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 7.316
And I take note of which tps features are available 0.541
And I shutdown Tails and wait for the computer to power off 4.647
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.831
After features/support/hooks.rb:330 0.358
After features/support/hooks.rb:100 0.007
Tags: @product
3:11.870
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 10.397
And I log in to a new session 29.614
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.590
And I plug USB drive "to_upgrade" 2.635
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.466
Then the running Tails is installed on USB drive "to_upgrade" 36.688
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.272
After features/support/hooks.rb:330 5.212
After features/support/hooks.rb:100 0.000
Tags: @product
3:8.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.046
Given a computer 0.566
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:51.803
Then all tps features from the old Tails version are active 1.781
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 8.321
And the expected persistent files created with the old Tails version are present in the filesystem 3.108
And all persistent directories from the old Tails version have safe access rights 2.565
After features/support/hooks.rb:330 1.818
After features/support/hooks.rb:100 0.005
8:27.673
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 17.195
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 10.861
And Tor is ready 22.275
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.765
Given I shutdown Tails and wait for the computer to power off 11.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.629
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.063
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.277
When the network is plugged 0.073
And Tor is ready 22.057
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.770
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.981
Given I shutdown Tails and wait for the computer to power off 8.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.786
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 2.149
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.080
And Tor is ready 51.457
Then the Upgrader considers the system as up-to-date 0.359
# 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.783
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.759
After features/support/hooks.rb:330 0.900
After features/support/hooks.rb:100 0.048
38.018
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 10.538
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.609
After features/support/hooks.rb:330 1.338
After features/support/hooks.rb:100 0.000