Project Number Date
test_Tails_ISO_stable 4772 04 Apr 2024, 19:08

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 16:6.080 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:29.256
Before features/support/hooks.rb:259 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 18.668
When I start Tails from USB drive "old" with network unplugged 1:5.905
Then the boot device has safe access rights 2.541
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.259
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 6.716
After features/support/hooks.rb:89 0.009
Tags: @product
1:51.143
Before features/support/hooks.rb:259 0.005
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:12.636
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 29.913
And I take note of which tps features are available 1.211
Then a Tails persistence partition exists on USB drive "old" 0.715
And I shutdown Tails and wait for the computer to power off 6.216
After features/support/hooks.rb:305 0.145
After features/support/hooks.rb:89 0.009
Tags: @product
2:32.000
Before features/support/hooks.rb:259 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.554
Then Tails is running from USB drive "old" 0.251
And all tps features are active 1.748
When I write some files expected to persist 1.473
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.098
And I take note of which tps features are available 0.369
And I shutdown Tails and wait for the computer to power off 4.237
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.516
After features/support/hooks.rb:305 0.123
After features/support/hooks.rb:89 0.009
Tags: @product
2:17.635
Before features/support/hooks.rb:259 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 9.556
And I log in to a new session 14.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.333
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.193
Then the running Tails is installed on USB drive "to_upgrade" 13.051
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:305 6.584
After features/support/hooks.rb:89 0.000
Tags: @product
1:54.556
Before features/support/hooks.rb:259 0.006
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.274
Then all tps features from the old Tails version are active 1.461
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.734
And the expected persistent files created with the old Tails version are present in the filesystem 1.301
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:305 0.552
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
5:30.842
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.728
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.049
And Tor is ready 16.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.245
Given I shutdown Tails and wait for the computer to power off 6.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.370
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.861
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.244
When the network is plugged 0.050
And Tor is ready 15.374
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.193
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.448
Given I shutdown Tails and wait for the computer to power off 4.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.478
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.696
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.264
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.051
And Tor is ready 18.578
Then the Upgrader considers the system as up-to-date 0.218
# 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 12.600
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.821
After features/support/hooks.rb:305 0.747
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
30.645
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.967
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.450
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 15.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.923
After features/support/hooks.rb:305 0.630
After features/support/hooks.rb:89 0.000