Project Number Date
test_Tails_ISO_stable 5120 26 Sep 2024, 08:42

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:43.362 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:20.185
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.732
When I start Tails from USB drive "old" with network unplugged 1:41.899
Then the boot device has safe access rights 4.111
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:326 7.310
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.452
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:27.182
Then Tails is running from USB drive "old" 0.460
And I create a persistent partition 31.572
And I take note of which tps features are available 1.825
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 6.369
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.615
Before features/support/hooks.rb:269 0.004
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.695
Then Tails is running from USB drive "old" 0.289
And all tps features are active 2.268
When I write some files expected to persist 1.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.471
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.309
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.414
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.816
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 9.392
And I log in to a new session 18.853
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.667
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.494
Then the running Tails is installed on USB drive "to_upgrade" 23.554
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 8.996
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.078
Before features/support/hooks.rb:269 0.006
Given a computer 0.285
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.403
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 3.509
After features/support/hooks.rb:326 0.673
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.705
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 12.774
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.653
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.081
And Tor is ready 27.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.817
Given I shutdown Tails and wait for the computer to power off 10.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.895
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.917
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.122
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.370
When the network is plugged 0.079
And Tor is ready 18.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.847
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.819
Given I shutdown Tails and wait for the computer to power off 6.657
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.802
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.090
And Tor is ready 20.191
Then the Upgrader considers the system as up-to-date 0.307
# 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 14.563
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.509
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.736
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.029
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.879
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 22.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.480
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.000