Project Number Date
test_Tails_ISO_stable 4835 09 May 2024, 12:23

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:57.383 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:7.573
Before features/support/hooks.rb:259 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.351
When I start Tails from USB drive "old" with network unplugged 1:30.939
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 3.555
After features/support/hooks.rb:89 0.047
Tags: @product
2:7.516
Before features/support/hooks.rb:259 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:23.179
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 33.165
And I take note of which tps features are available 1.528
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.293
After features/support/hooks.rb:305 0.190
After features/support/hooks.rb:89 0.010
Tags: @product
2:49.675
Before features/support/hooks.rb:259 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.364
Then Tails is running from USB drive "old" 0.439
And all tps features are active 2.245
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.791
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.279
After features/support/hooks.rb:305 0.120
After features/support/hooks.rb:89 0.009
Tags: @product
2:21.139
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.972
And I log in to a new session 18.178
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.316
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.231
Then the running Tails is installed on USB drive "to_upgrade" 16.611
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:305 3.114
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.033
Before features/support/hooks.rb:259 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.365
Then all tps features from the old Tails version are active 2.898
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.100
And the expected persistent files created with the old Tails version are present in the filesystem 1.573
And all persistent directories from the old Tails version have safe access rights 2.515
After features/support/hooks.rb:305 0.685
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:40.252
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 12.117
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.077
And Tor is ready 19.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.114
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.669
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.299
When the network is plugged 0.034
And Tor is ready 20.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.999
Given I shutdown Tails and wait for the computer to power off 4.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.736
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.040
And Tor is ready 16.994
Then the Upgrader considers the system as up-to-date 10.706
# 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 15.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.999
After features/support/hooks.rb:305 0.744
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
36.192
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 10.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.487
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 17.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.463
After features/support/hooks.rb:305 0.909
After features/support/hooks.rb:89 0.000