Project Number Date
test_Tails_ISO_stable 5296 27 Nov 2024, 12:57

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 22:10.209 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:46.085
Before features/support/hooks.rb:269 0.006
Given a computer 2.116
And I create a 7200 MiB disk named "old" 1.873
And I plug USB drive "old" 1.453
And I write an old version of the Tails USB image to disk "old" 56.258
When I start Tails from USB drive "old" with network unplugged 1:40.105
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 7.471
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.903
Before features/support/hooks.rb:269 0.005
Given a computer 1.629
And I start Tails from USB drive "old" with network unplugged and I login 1:30.397
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 35.987
And I take note of which tps features are available 1.912
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 10.801
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
3:22.708
Before features/support/hooks.rb:269 0.004
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.013
Then Tails is running from USB drive "old" 2.050
And all tps features are active 2.564
When I write some files expected to persist 2.238
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.070
And I take note of which tps features are available 0.715
And I shutdown Tails and wait for the computer to power off 7.174
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.903
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.009
Tags: @product
3:20.035
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 27.477
And I log in to a new session 25.259
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.383
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.620
Then the running Tails is installed on USB drive "to_upgrade" 23.214
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 2.961
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.050
Before features/support/hooks.rb:269 0.006
Given a computer 0.293
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.915
Then all tps features from the old Tails version are active 1.901
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.641
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 4.428
After features/support/hooks.rb:326 1.212
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:10.924
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 32.673
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.561
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.129
And Tor is ready 20.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.528
Given I shutdown Tails and wait for the computer to power off 11.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.655
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.438
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.341
When the network is plugged 0.072
And Tor is ready 20.933
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.556
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.976
Given I shutdown Tails and wait for the computer to power off 4.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.923
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.083
And Tor is ready 17.156
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 15.944
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:326 0.817
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.501
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.985
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 21.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.874
After features/support/hooks.rb:326 0.947
After features/support/hooks.rb:100 0.000