Project Number Date
test_Tails_ISO_devel 3383 09 May 2024, 17: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 18:52.582 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:2.666
Before features/support/hooks.rb:259 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.978
When I start Tails from USB drive "old" with network unplugged 1:28.179
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:305 3.526
After features/support/hooks.rb:89 0.014
Tags: @product
2:13.354
Before features/support/hooks.rb:259 0.008
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:29.244
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 32.771
And I take note of which tps features are available 1.551
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.393
After features/support/hooks.rb:305 0.173
After features/support/hooks.rb:89 0.008
Tags: @product
2:51.337
Before features/support/hooks.rb:259 0.009
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.950
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.093
When I write some files expected to persist 1.711
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.722
And I take note of which tps features are available 0.617
And I shutdown Tails and wait for the computer to power off 4.439
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.638
After features/support/hooks.rb:305 0.122
After features/support/hooks.rb:89 0.010
Tags: @product
2:32.732
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 12.180
And I log in to a new session 18.503
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.407
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.042
Then the running Tails is installed on USB drive "to_upgrade" 21.752
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:305 2.281
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.609
Before features/support/hooks.rb:259 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.737
Then all tps features from the old Tails version are active 2.380
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.967
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.390
After features/support/hooks.rb:305 0.632
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:21.971
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.025
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.064
And Tor is ready 18.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.837
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.765
Given I shutdown Tails and wait for the computer to power off 8.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.400
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.388
And the file system changes introduced in version 6.2~testoverlayfs are present 0.262
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.291
When the network is plugged 0.044
And Tor is ready 18.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.875
Given I shutdown Tails and wait for the computer to power off 4.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.190
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.037
And Tor is ready 19.854
Then the Upgrader considers the system as up-to-date 0.316
# 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.740
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.896
After features/support/hooks.rb:305 0.751
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
33.910
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.695
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 15.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.580
After features/support/hooks.rb:305 1.386
After features/support/hooks.rb:89 0.000