Project Number Date
test_Tails_ISO_20979-pdfarranger 1 28 May 2025, 03:21

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.746 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:1.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.109
When I start Tails from USB drive "old" with network unplugged 1:24.420
Then the boot device has safe access rights 3.073
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.269
After features/support/hooks.rb:330 3.620
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:22.497
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.051
And I take note of which tps features are available 1.907
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.181
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.428
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.794
When I write some files expected to persist 1.811
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.959
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 6.544
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.140
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.758
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 without a persistent partition and stopped at Tails Greeter's login screen 10.966
And I log in to a new session 18.536
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.042
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.040
Then the running Tails is installed on USB drive "to_upgrade" 28.399
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 2.085
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.645
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.208
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.652
After features/support/hooks.rb:330 1.289
After features/support/hooks.rb:100 0.009
6:39.691
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.491
And no SquashFS delta is installed 0.466
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.069
And Tor is ready 23.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.359
Given I shutdown Tails and wait for the computer to power off 8.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.653
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.315
When the network is plugged 0.063
And Tor is ready 17.281
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.491
Given I shutdown Tails and wait for the computer to power off 4.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.654
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.056
And Tor is ready 19.078
Then the Upgrader considers the system as up-to-date 0.303
# 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.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.736
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.041
58.121
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 9.348
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.633
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 47.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.568
After features/support/hooks.rb:330 1.270
After features/support/hooks.rb:100 0.000