Project Number Date
test_Tails_ISO_stable 5310 03 Dec 2024, 12:39

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:11.696 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:45.269
Before features/support/hooks.rb:269 0.005
Given a computer 0.277
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 34.110
When I start Tails from USB drive "old" with network unplugged 2:4.343
Then the boot device has safe access rights 4.119
And Tails is running from USB drive "old" 0.415
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.446
And I unplug USB drive "old" 0.274
After features/support/hooks.rb:326 3.650
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.376
Before features/support/hooks.rb:269 0.006
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login 1:33.819
Then Tails is running from USB drive "old" 0.422
And I create a persistent partition 34.424
And I take note of which tps features are available 2.090
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 8.460
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.309
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.780
Then Tails is running from USB drive "old" 0.474
And all tps features are active 2.151
When I write some files expected to persist 1.905
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.679
And I take note of which tps features are available 0.578
And I shutdown Tails and wait for the computer to power off 4.375
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.550
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.466
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 12.257
And I log in to a new session 20.252
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.972
And I plug USB drive "to_upgrade" 2.562
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.117
Then the running Tails is installed on USB drive "to_upgrade" 23.879
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.445
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.471
Before features/support/hooks.rb:269 0.008
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.175
Then all tps features from the old Tails version are active 2.065
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.616
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 2.524
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:16.257
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 13.113
And no SquashFS delta is installed 0.261
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.086
And Tor is ready 48.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.236
Given I shutdown Tails and wait for the computer to power off 11.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.962
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.337
When the network is plugged 0.073
And Tor is ready 21.772
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.935
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.020
Given I shutdown Tails and wait for the computer to power off 4.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.348
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 2.261
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.584
When the network is plugged 0.081
And Tor is ready 20.323
Then the Upgrader considers the system as up-to-date 0.299
# 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.840
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.403
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.544
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 10.638
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.561
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.801
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 21.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.836
After features/support/hooks.rb:326 0.925
After features/support/hooks.rb:100 0.000