Project Number Date
test_Tails_ISO_20522-ocr-more 35 20 Jan 2025, 05: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 20:24.237 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:9.600
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.066
When I start Tails from USB drive "old" with network unplugged 1:34.284
Then the boot device has safe access rights 2.877
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.864
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:38.207
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 32.554
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.278
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.007
Tags: @product
2:49.656
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.416
Then Tails is running from USB drive "old" 0.537
And all tps features are active 2.210
When I write some files expected to persist 2.047
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.424
And all persistent directories from the old Tails version have safe access rights 3.040
And I take note of which tps features are available 0.590
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.591
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.903
Before features/support/hooks.rb:269 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 10.550
And I log in to a new session 19.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.833
Then the running Tails is installed on USB drive "to_upgrade" 17.349
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 7.178
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.936
Before features/support/hooks.rb:269 0.006
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.161
Then all tps features from the old Tails version are active 1.902
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.735
After features/support/hooks.rb:326 1.038
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:43.456
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.374
And no SquashFS delta is installed 0.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.132
And Tor is ready 22.105
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.143
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.757
Given I shutdown Tails and wait for the computer to power off 1:28.789
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.042
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.613
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.400
When the network is plugged 0.082
And Tor is ready 19.359
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.670
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.501
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.325
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.507
When the network is plugged 0.101
And Tor is ready 16.988
Then the Upgrader considers the system as up-to-date 0.296
# 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.665
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.819
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.710
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.079
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000