Project Number Date
test_Tails_ISO_feature-arti 108 06 Jul 2025, 17:45

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 20:36.659 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:11.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.618
When I start Tails from USB drive "old" with network unplugged 1:35.528
Then the boot device has safe access rights 3.559
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.278
After features/support/hooks.rb:330 7.629
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:35.638
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.489
And I take note of which tps features are available 2.449
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.829
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.915
Then Tails is running from USB drive "old" 0.434
And all tps features are active 2.244
When I write some files expected to persist 1.718
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 3.593
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 6.589
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.565
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.708
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 10.576
And I log in to a new session 21.041
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.847
And I plug USB drive "to_upgrade" 2.584
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.154
Then the running Tails is installed on USB drive "to_upgrade" 29.008
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:330 2.254
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.298
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.795
Then all tps features from the old Tails version are active 2.504
And Tails is running from USB drive "to_upgrade" 0.519
And the boot device has safe access rights 3.980
And the expected persistent files created with the old Tails version are present in the filesystem 1.746
And all persistent directories from the old Tails version have safe access rights 2.846
After features/support/hooks.rb:330 1.173
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:46.703
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.166
And no SquashFS delta is installed 0.221
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.481
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.696
When the network is plugged 0.096
And Tor is ready 22.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.008
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.255
Given I shutdown Tails and wait for the computer to power off 8.766
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.006
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.293
When the network is plugged 0.064
And Tor is ready 19.086
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.771
Given I shutdown Tails and wait for the computer to power off 4.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.183
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 2.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
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.269
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.080
And Tor is ready 18.707
Then the Upgrader considers the system as up-to-date 0.311
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.499
After features/support/hooks.rb:330 0.681
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:0.160
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 10.020
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 48.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.656
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.000