Project Number Date
test_Tails_ISO_devel 3562 26 Oct 2024, 13: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 19:50.162 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:18.894
Before features/support/hooks.rb:269 0.008
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.131
And I write an old version of the Tails USB image to disk "old" 31.799
When I start Tails from USB drive "old" with network unplugged 1:40.841
Then the boot device has safe access rights 3.665
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.755
After features/support/hooks.rb:100 0.015
Tags: @product
2:13.837
Before features/support/hooks.rb:269 0.010
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:27.501
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 33.002
And I take note of which tps features are available 2.527
Then a Tails persistence partition exists on USB drive "old" 1.104
And I shutdown Tails and wait for the computer to power off 9.071
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.013
Tags: @product
2:59.036
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.069
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.341
When I write some files expected to persist 2.001
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.622
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.683
After features/support/hooks.rb:326 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.530
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.530
And I log in to a new session 20.281
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.515
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.914
Then the running Tails is installed on USB drive "to_upgrade" 23.175
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.567
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.254
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.449
Then all tps features from the old Tails version are active 1.781
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.185
And the expected persistent files created with the old Tails version are present in the filesystem 1.820
And all persistent directories from the old Tails version have safe access rights 2.449
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:45.088
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 20.173
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.087
And Tor is ready 26.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.276
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.607
Given I shutdown Tails and wait for the computer to power off 13.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.779
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.285
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.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.371
When the network is plugged 0.081
And Tor is ready 20.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.237
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.945
Given I shutdown Tails and wait for the computer to power off 4.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.811
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.568
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.074
And Tor is ready 17.873
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 13.967
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.957
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.520
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.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.627
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.981
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 22.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.494
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000