Project Number Date
test_Tails_ISO_stable 4725 18 Mar 2024, 15:17

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 17:40.459 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:38.551
Before features/support/hooks.rb:245 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.131
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 21.034
When I start Tails from USB drive "old" with network unplugged 1:12.211
Then the boot device has safe access rights 2.955
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:291 6.622
After features/support/hooks.rb:75 0.009
Tags: @product
1:56.578
Before features/support/hooks.rb:245 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:15.590
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 30.731
And I take note of which tps features are available 1.843
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 7.199
After features/support/hooks.rb:291 0.130
After features/support/hooks.rb:75 0.008
Tags: @product
2:34.475
Before features/support/hooks.rb:245 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.868
Then Tails is running from USB drive "old" 0.368
And all tps features are active 1.943
When I write some files expected to persist 1.687
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.424
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.020
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.861
After features/support/hooks.rb:291 0.141
After features/support/hooks.rb:75 0.011
Tags: @product
2:32.561
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.346
And I log in to a new session 15.757
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.485
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.602
Then the running Tails is installed on USB drive "to_upgrade" 13.506
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:291 6.635
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.612
Before features/support/hooks.rb:245 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.455
Then all tps features from the old Tails version are active 1.789
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.092
And the expected persistent files created with the old Tails version are present in the filesystem 1.345
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:291 0.757
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:20.049
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.232
And no SquashFS delta is installed 0.621
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.038
And Tor is ready 17.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.831
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.326
Given I shutdown Tails and wait for the computer to power off 8.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.419
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.926
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# 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.266
When the network is plugged 0.059
And Tor is ready 44.523
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.613
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.187
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.493
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.835
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.276
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.033
And Tor is ready 16.009
Then the Upgrader considers the system as up-to-date 0.248
# 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.662
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.090
After features/support/hooks.rb:291 0.815
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
33.630
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.640
But a current signing key is available on our website 0.000
When the network is plugged 0.197
And Tor is ready 15.487
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.791
After features/support/hooks.rb:291 0.606
After features/support/hooks.rb:75 0.000