Project Number Date
test_Tails_ISO_stable 5546 03 Apr 2025, 02:40

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:30.636 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
1:55.468
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.148
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 29.453
When I start Tails from USB drive "old" with network unplugged 1:20.792
Then the boot device has safe access rights 3.018
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.570
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login 1:24.089
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 30.458
And I take note of which tps features are available 1.586
Then a Tails persistence partition exists on USB drive "old" 0.751
And I shutdown Tails and wait for the computer to power off 8.188
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.006
Tags: @product
2:57.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.887
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.944
When I write some files expected to persist 1.626
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.539
And all persistent directories from the old Tails version have safe access rights 3.286
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.060
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.879
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.093
And I log in to a new session 17.460
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.784
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.539
Then the running Tails is installed on USB drive "to_upgrade" 24.230
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 0.898
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.142
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.260
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.181
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:330 1.497
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:52.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.307
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.450
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.069
And Tor is ready 20.619
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.746
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.977
Given I shutdown Tails and wait for the computer to power off 8.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.416
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.281
When the network is plugged 0.067
And Tor is ready 20.500
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.475
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.756
Given I shutdown Tails and wait for the computer to power off 6.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.059
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.836
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.079
And Tor is ready 46.351
Then the Upgrader considers the system as up-to-date 0.297
# 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.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.581
After features/support/hooks.rb:330 0.780
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
58.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.676
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 47.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
After features/support/hooks.rb:330 0.665
After features/support/hooks.rb:100 0.000