Project Number Date
test_Tails_ISO_devel 3303 29 Feb 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 18:40.241 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:46.262
Before features/support/hooks.rb:245 0.008
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 33.610
When I start Tails from USB drive "old" with network unplugged 1:7.318
Then the boot device has safe access rights 3.044
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:291 3.556
After features/support/hooks.rb:75 0.059
Tags: @product
2:9.912
Before features/support/hooks.rb:245 0.008
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:15.572
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 41.984
And I take note of which tps features are available 1.916
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 9.038
After features/support/hooks.rb:291 0.231
After features/support/hooks.rb:75 0.013
Tags: @product
2:33.789
Before features/support/hooks.rb:245 0.009
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.344
Then Tails is running from USB drive "old" 0.372
And all tps features are active 1.756
When I write some files expected to persist 1.562
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.506
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.839
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.011
Tags: @product
2:32.121
Before features/support/hooks.rb:245 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 10.322
And I log in to a new session 17.001
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.738
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.223
Then the running Tails is installed on USB drive "to_upgrade" 12.967
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:291 0.861
After features/support/hooks.rb:75 0.000
Tags: @product
2:17.490
Before features/support/hooks.rb:245 0.010
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.782
Then all tps features from the old Tails version are active 1.499
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.003
And the expected persistent files created with the old Tails version are present in the filesystem 1.397
And all persistent directories from the old Tails version have safe access rights 2.293
After features/support/hooks.rb:291 0.858
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:45.092
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.653
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.062
And Tor is ready 19.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.913
Given I shutdown Tails and wait for the computer to power off 6.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.599
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 1.781
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.233
When the network is plugged 0.030
And Tor is ready 17.950
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.433
Given I shutdown Tails and wait for the computer to power off 4.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.322
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.599
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.029
And Tor is ready 13.916
Then the Upgrader considers the system as up-to-date 10.737
# 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 13.507
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.808
After features/support/hooks.rb:291 0.671
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
35.571
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.874
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.836
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.886
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.584
After features/support/hooks.rb:291 0.613
After features/support/hooks.rb:75 0.000