Project Number Date
test_Tails_ISO_feature-arti 112 15 Jul 2025, 17:31

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:56.432 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:9.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.329
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.607
When I start Tails from USB drive "old" with network unplugged 1:32.156
Then the boot device has safe access rights 3.637
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 4.510
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login 1:33.055
Then Tails is running from USB drive "old" 0.427
And I create a persistent partition 32.099
And I take note of which tps features are available 2.095
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 9.803
After features/support/hooks.rb:330 0.233
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.453
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:43.340
Then Tails is running from USB drive "old" 0.517
And all tps features are active 2.350
When I write some files expected to persist 1.765
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.517
And I take note of which tps features are available 0.519
And I shutdown Tails and wait for the computer to power off 4.198
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.339
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.705
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 without a persistent partition and stopped at Tails Greeter's login screen 11.076
And I log in to a new session 19.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.779
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.764
Then the running Tails is installed on USB drive "to_upgrade" 29.143
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 0.382
After features/support/hooks.rb:330 2.446
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.040
Then all tps features from the old Tails version are active 1.682
And Tails is running from USB drive "to_upgrade" 0.430
And the boot device has safe access rights 3.840
And the expected persistent files created with the old Tails version are present in the filesystem 2.369
And all persistent directories from the old Tails version have safe access rights 3.587
After features/support/hooks.rb:330 1.216
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:8.743
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 12.186
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.631
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.851
When the network is plugged 0.396
And Tor is ready 20.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.530
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.630
Given I shutdown Tails and wait for the computer to power off 9.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.529
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.299
When the network is plugged 0.083
And Tor is ready 22.101
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.340
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.182
Given I shutdown Tails and wait for the computer to power off 6.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.512
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.066
And Tor is ready 21.370
Then the Upgrader considers the system as up-to-date 0.333
# 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 17.373
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.072
After features/support/hooks.rb:330 0.759
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
40.081
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.992
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.572
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.148
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.139
And Tor is ready 17.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.641
After features/support/hooks.rb:330 2.199
After features/support/hooks.rb:100 0.000