Project Number Date
test_Tails_ISO_stable 5330 12 Dec 2024, 13: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 19:4.108 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:4.994
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.736
When I start Tails from USB drive "old" with network unplugged 1:29.982
Then the boot device has safe access rights 2.984
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.852
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:22.598
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 30.864
And I take note of which tps features are available 1.489
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 6.573
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.892
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.736
Then Tails is running from USB drive "old" 0.390
And all tps features are active 1.865
When I write some files expected to persist 1.696
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.378
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.080
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 11.079
And I log in to a new session 19.958
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.782
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.505
Then the running Tails is installed on USB drive "to_upgrade" 19.988
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.707
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.668
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.393
Then all tps features from the old Tails version are active 1.651
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.349
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.316
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
6:20.881
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.960
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.071
And Tor is ready 21.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.083
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.411
Given I shutdown Tails and wait for the computer to power off 8.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.729
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.199
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.260
When the network is plugged 0.067
And Tor is ready 17.839
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.241
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.771
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.639
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.031
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.558
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.334
When the network is plugged 0.084
And Tor is ready 17.299
Then the Upgrader considers the system as up-to-date 0.362
# 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.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.947
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
1:3.738
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.715
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.888
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 49.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.637
After features/support/hooks.rb:326 0.884
After features/support/hooks.rb:100 0.000