Project Number Date
test_Tails_ISO_stable 5464 17 Feb 2025, 14:57

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 21:31.769 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:24.290
Before features/support/hooks.rb:269 0.005
Given a computer 1.350
And I create a 7200 MiB disk named "old" 0.478
And I plug USB drive "old" 1.256
And I write an old version of the Tails USB image to disk "old" 41.633
When I start Tails from USB drive "old" with network unplugged 1:34.979
Then the boot device has safe access rights 3.458
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:326 3.752
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.591
Before features/support/hooks.rb:269 0.006
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login 1:34.508
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 33.048
And I take note of which tps features are available 2.137
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 9.398
After features/support/hooks.rb:326 0.321
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.310
Before features/support/hooks.rb:269 0.006
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.356
Then Tails is running from USB drive "old" 0.869
And all tps features are active 2.898
When I write some files expected to persist 2.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 3.090
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 4.284
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.811
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.013
Tags: @product
3:0.577
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 23.268
And I log in to a new session 21.759
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.993
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.731
Then the running Tails is installed on USB drive "to_upgrade" 27.707
And I unplug USB drive "to_upgrade" 0.295
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 3.294
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.357
Before features/support/hooks.rb:269 0.009
Given a computer 0.301
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.717
Then all tps features from the old Tails version are active 2.178
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.438
And the expected persistent files created with the old Tails version are present in the filesystem 1.552
And all persistent directories from the old Tails version have safe access rights 2.831
After features/support/hooks.rb:326 0.975
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:18.577
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 25.880
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.102
And Tor is ready 23.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.671
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.146
Given I shutdown Tails and wait for the computer to power off 11.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.360
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.596
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.326
When the network is plugged 0.106
And Tor is ready 19.789
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.066
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.431
Given I shutdown Tails and wait for the computer to power off 4.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.493
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.351
And the file system changes introduced in version 6.3~testoverlayfs are present 0.572
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.565
When the network is plugged 0.122
And Tor is ready 16.401
Then the Upgrader considers the system as up-to-date 0.385
# 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.745
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.328
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.065
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.554
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 22.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.256
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.000