Project Number Date
test_Tails_ISO_stable 5420 27 Jan 2025, 15:17

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 20:5.599 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:25.480
Before features/support/hooks.rb:269 0.014
Given a computer 0.659
And I create a 7200 MiB disk named "old" 0.126
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 35.875
When I start Tails from USB drive "old" with network unplugged 1:43.567
Then the boot device has safe access rights 3.146
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.572
After features/support/hooks.rb:100 0.015
Tags: @product
2:19.157
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:31.320
Then Tails is running from USB drive "old" 0.460
And I create a persistent partition 36.016
And I take note of which tps features are available 1.733
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.008
Tags: @product
3:8.433
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.974
Then Tails is running from USB drive "old" 0.424
And all tps features are active 2.310
When I write some files expected to persist 1.955
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.517
And all persistent directories from the old Tails version have safe access rights 3.011
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.710
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.639
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.869
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 11.882
And I log in to a new session 20.417
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.638
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.224
Then the running Tails is installed on USB drive "to_upgrade" 25.839
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.455
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.640
Before features/support/hooks.rb:269 0.004
Given a computer 0.294
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.952
Then all tps features from the old Tails version are active 3.448
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.931
And the expected persistent files created with the old Tails version are present in the filesystem 1.702
And all persistent directories from the old Tails version have safe access rights 2.940
After features/support/hooks.rb:326 0.937
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:29.270
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.922
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.248
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.079
And Tor is ready 18.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.538
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.657
Given I shutdown Tails and wait for the computer to power off 8.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.476
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.309
When the network is plugged 0.076
And Tor is ready 20.975
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.414
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.833
Given I shutdown Tails and wait for the computer to power off 4.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.149
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.392
When the network is plugged 0.105
And Tor is ready 17.994
Then the Upgrader considers the system as up-to-date 0.389
# 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 16.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.337
After features/support/hooks.rb:326 0.877
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
31.747
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.654
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
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.089
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 15.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.591
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.000