Project Number Date
test_Tails_ISO_stable 5751 30 Jun 2025, 12:52

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:47.755 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:7.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.975
When I start Tails from USB drive "old" with network unplugged 1:31.090
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.284
After features/support/hooks.rb:330 9.464
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.636
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:32.879
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 33.024
And I take note of which tps features are available 1.585
Then a Tails persistence partition exists on USB drive "old" 0.975
And I shutdown Tails and wait for the computer to power off 8.608
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.681
Then Tails is running from USB drive "old" 0.300
And all tps features are active 1.868
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.251
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.042
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.888
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 without a persistent partition and stopped at Tails Greeter's login screen 11.086
And I log in to a new session 19.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.671
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.728
Then the running Tails is installed on USB drive "to_upgrade" 25.872
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:330 2.190
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.902
Then all tps features from the old Tails version are active 1.771
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.837
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:330 1.438
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:50.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.468
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.419
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.753
When the network is plugged 0.105
And Tor is ready 20.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.205
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.713
Given I shutdown Tails and wait for the computer to power off 10.861
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.658
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.080
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.508
When the network is plugged 0.083
And Tor is ready 19.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.043
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.767
Given I shutdown Tails and wait for the computer to power off 4.802
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.245
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.053
And the file system changes introduced in version 6.3~testoverlayfs are present 0.451
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.135
And Tor is ready 19.263
Then the Upgrader considers the system as up-to-date 0.416
# 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 15.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.707
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.376
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 with a persistent partition enabled and logged in 12.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.076
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.110
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.236
After features/support/hooks.rb:330 1.009
After features/support/hooks.rb:100 0.000