Project Number Date
test_Tails_ISO_devel 3806 12 May 2025, 20:37

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:17.260 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:24.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 32.618
When I start Tails from USB drive "old" with network unplugged 1:46.002
Then the boot device has safe access rights 3.265
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.699
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.676
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:29.031
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 31.218
And I take note of which tps features are available 2.393
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.638
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.450
Then Tails is running from USB drive "old" 0.633
And all tps features are active 2.661
When I write some files expected to persist 1.975
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.751
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.539
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.013
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.889
And I log in to a new session 20.904
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.495
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.042
Then the running Tails is installed on USB drive "to_upgrade" 24.431
And I unplug USB drive "to_upgrade" 0.632
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.158
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.548
After features/support/hooks.rb:330 1.065
After features/support/hooks.rb:100 0.008
7:1.671
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 13.220
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.240
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.466
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.612
When the network is plugged 0.076
And Tor is ready 25.166
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.832
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.210
Given I shutdown Tails and wait for the computer to power off 8.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.176
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.326
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
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.304
When the network is plugged 0.079
And Tor is ready 48.708
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.589
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.750
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.583
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.075
And Tor is ready 17.789
Then the Upgrader considers the system as up-to-date 0.335
# 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.128
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.170
After features/support/hooks.rb:330 0.796
After features/support/hooks.rb:100 0.046
39.867
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 10.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.811
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 21.995
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
After features/support/hooks.rb:330 1.620
After features/support/hooks.rb:100 0.000