Project Number Date
test_Tails_ISO_stable 5663 20 May 2025, 08:51

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:28.291 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:6.287
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.383
When I start Tails from USB drive "old" with network unplugged 1:29.806
Then the boot device has safe access rights 2.890
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:330 3.701
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:33.933
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 30.478
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.748
And I shutdown Tails and wait for the computer to power off 6.619
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.559
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.185
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.646
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 6.143
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.942
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.328
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.807
And I log in to a new session 18.820
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.456
Then the running Tails is installed on USB drive "to_upgrade" 20.897
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.181
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.873
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.253
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.340
After features/support/hooks.rb:330 1.314
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:54.692
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 17.784
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.079
And Tor is ready 22.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.169
Given I shutdown Tails and wait for the computer to power off 8.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.172
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.366
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.286
When the network is plugged 0.064
And Tor is ready 15.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.656
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.812
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.283
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.658
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.084
And Tor is ready 47.339
Then the Upgrader considers the system as up-to-date 0.325
# 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 14.918
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.809
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.935
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 9.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.535
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 16.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.544
After features/support/hooks.rb:330 0.906
After features/support/hooks.rb:100 0.000