Project Number Date
test_Tails_ISO_stable 5228 28 Oct 2024, 19:07

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 21:34.100 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:51.295
Before features/support/hooks.rb:269 0.005
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 1:4.897
When I start Tails from USB drive "old" with network unplugged 1:40.631
Then the boot device has safe access rights 3.279
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.299
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.575
Before features/support/hooks.rb:269 0.008
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:29.884
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 31.873
And I take note of which tps features are available 1.907
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 8.397
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.823
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.436
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.721
When I write some files expected to persist 2.045
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.912
And I take note of which tps features are available 2.258
And I shutdown Tails and wait for the computer to power off 4.449
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.681
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.132
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 25.218
And I log in to a new session 20.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.223
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.783
Then the running Tails is installed on USB drive "to_upgrade" 22.814
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.265
After features/support/hooks.rb:326 3.662
After features/support/hooks.rb:100 0.000
Tags: @product
2:43.636
Before features/support/hooks.rb:269 0.007
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.864
Then all tps features from the old Tails version are active 3.605
And Tails is running from USB drive "to_upgrade" 0.464
And the boot device has safe access rights 3.411
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.577
After features/support/hooks.rb:326 1.012
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:48.586
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 18.220
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.257
And Tor is ready 23.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.115
Given I shutdown Tails and wait for the computer to power off 10.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.005
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 6.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.352
When the network is plugged 0.227
And Tor is ready 19.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.256
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.814
Given I shutdown Tails and wait for the computer to power off 4.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.145
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.410
And the file system changes introduced in version 6.3~testoverlayfs are present 0.743
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.379
When the network is plugged 0.065
And Tor is ready 19.408
Then the Upgrader considers the system as up-to-date 0.373
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.004
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
43.050
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 11.511
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.115
And the signing key used by the Upgrader is outdated 0.831
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 22.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.345
After features/support/hooks.rb:326 1.092
After features/support/hooks.rb:100 0.000