Project Number Date
test_Tails_ISO_stable 5439 03 Feb 2025, 12:36

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.417 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:57.467
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 30.121
When I start Tails from USB drive "old" with network unplugged 1:21.971
Then the boot device has safe access rights 3.071
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.564
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.952
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:22.556
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 32.095
And I take note of which tps features are available 1.719
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 8.291
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.527
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.200
Then Tails is running from USB drive "old" 1.436
And all tps features are active 1.880
When I write some files expected to persist 1.732
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.358
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.315
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.007
Tags: @product
2:26.587
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.841
And I log in to a new session 17.947
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.447
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.472
Then the running Tails is installed on USB drive "to_upgrade" 20.037
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.541
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.292
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.036
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.451
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:41.154
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.357
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.064
And Tor is ready 20.587
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.421
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.212
Given I shutdown Tails and wait for the computer to power off 9.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.167
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.310
When the network is plugged 0.079
And Tor is ready 19.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.137
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.437
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.734
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.930
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.299
When the network is plugged 0.065
And Tor is ready 19.773
Then the Upgrader considers the system as up-to-date 0.310
# 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.180
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.902
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
33.437
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 9.976
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.049
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 17.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.173
After features/support/hooks.rb:326 0.598
After features/support/hooks.rb:100 0.000