Project Number Date
test_Tails_ISO_stable 4978 29 Jul 2024, 12:37

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 20:45.842 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
3:5.311
Before features/support/hooks.rb:269 0.010
Given a computer 0.365
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 1:10.447
When I start Tails from USB drive "old" with network unplugged 1:48.510
Then the boot device has safe access rights 3.527
And Tails is running from USB drive "old" 0.424
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.428
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:326 7.386
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.452
Before features/support/hooks.rb:269 0.007
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login 1:40.778
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 33.313
And I take note of which tps features are available 2.662
Then a Tails persistence partition exists on USB drive "old" 0.985
And I shutdown Tails and wait for the computer to power off 9.001
After features/support/hooks.rb:326 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.804
Before features/support/hooks.rb:269 0.006
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.163
Then Tails is running from USB drive "old" 0.514
And all tps features are active 2.417
When I write some files expected to persist 1.956
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 2.780
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.128
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.391
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.967
Before features/support/hooks.rb:269 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 11.761
And I log in to a new session 19.512
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.536
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.678
Then the running Tails is installed on USB drive "to_upgrade" 18.696
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 6.633
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.731
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.268
Then all tps features from the old Tails version are active 1.662
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.124
And the expected persistent files created with the old Tails version are present in the filesystem 1.635
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:326 0.631
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.304
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 11.148
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.070
And Tor is ready 22.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.704
Given I shutdown Tails and wait for the computer to power off 8.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.732
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.288
When the network is plugged 0.048
And Tor is ready 20.005
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.246
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.488
Given I shutdown Tails and wait for the computer to power off 4.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.363
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.036
And Tor is ready 19.955
Then the Upgrader considers the system as up-to-date 0.312
# 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 17.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.089
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.270
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.944
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.881
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 18.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.142
After features/support/hooks.rb:326 1.203
After features/support/hooks.rb:100 0.000