Project Number Date
test_Tails_ISO_devel 3394 19 May 2024, 13:37

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.817 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.900
Before features/support/hooks.rb:259 0.007
Given a computer 0.349
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.866
When I start Tails from USB drive "old" with network unplugged 1:24.771
Then the boot device has safe access rights 2.850
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 3.502
After features/support/hooks.rb:89 0.064
Tags: @product
2:13.305
Before features/support/hooks.rb:259 0.008
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:27.684
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 34.442
And I take note of which tps features are available 1.417
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.436
After features/support/hooks.rb:305 0.184
After features/support/hooks.rb:89 0.012
Tags: @product
2:52.890
Before features/support/hooks.rb:259 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.112
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.155
When I write some files expected to persist 1.704
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.500
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.338
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.329
After features/support/hooks.rb:305 0.107
After features/support/hooks.rb:89 0.008
Tags: @product
2:30.682
Before features/support/hooks.rb:259 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 11.975
And I log in to a new session 17.519
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.585
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.200
Then the running Tails is installed on USB drive "to_upgrade" 19.639
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:305 2.013
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.455
Before features/support/hooks.rb:259 0.008
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.862
Then all tps features from the old Tails version are active 1.888
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.601
And all persistent directories from the old Tails version have safe access rights 2.367
After features/support/hooks.rb:305 0.883
After features/support/hooks.rb:89 0.065
Tags: @product @automatic_upgrade
6:54.436
Before features/support/hooks.rb:259 0.060
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.292
And no SquashFS delta is installed 1.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.666
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.043
And Tor is ready 19.587
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.258
Given I shutdown Tails and wait for the computer to power off 8.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.884
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.252
When the network is plugged 0.049
And Tor is ready 47.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.161
Given I shutdown Tails and wait for the computer to power off 4.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.518
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.507
And the file system changes introduced in version 6.3~testoverlayfs are present 0.571
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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.037
And Tor is ready 19.443
Then the Upgrader considers the system as up-to-date 0.342
# 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.920
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.032
After features/support/hooks.rb:305 0.847
After features/support/hooks.rb:89 0.036
Tags: @product @automatic_upgrade
40.147
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.594
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 18.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.614
After features/support/hooks.rb:305 1.550
After features/support/hooks.rb:89 0.000