Project Number Date
test_Tails_ISO_stable 5396 15 Jan 2025, 19:49

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:32.601 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:1.347
Before features/support/hooks.rb:269 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.636
When I start Tails from USB drive "old" with network unplugged 1:24.490
Then the boot device has safe access rights 3.637
And Tails is running from USB drive "old" 0.601
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.017
Before features/support/hooks.rb:269 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:25.097
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 33.394
And I take note of which tps features are available 1.435
Then a Tails persistence partition exists on USB drive "old" 1.136
And I shutdown Tails and wait for the computer to power off 8.433
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.568
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.153
Then Tails is running from USB drive "old" 1.396
And all tps features are active 1.933
When I write some files expected to persist 3.435
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 3.459
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.596
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.318
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.665
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.335
And I log in to a new session 18.878
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.843
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.102
Then the running Tails is installed on USB drive "to_upgrade" 21.656
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.092
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.968
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.941
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.756
After features/support/hooks.rb:326 0.976
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:48.922
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.304
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.068
And Tor is ready 22.568
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.666
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.558
Given I shutdown Tails and wait for the computer to power off 1:17.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.566
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.130
And the file system changes introduced in version 6.2~testoverlayfs are present 0.440
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.479
# 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.311
When the network is plugged 0.076
And Tor is ready 21.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.251
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.268
Given I shutdown Tails and wait for the computer to power off 4.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.538
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.647
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.473
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.073
And Tor is ready 19.209
Then the Upgrader considers the system as up-to-date 0.327
# 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.973
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.058
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
51.110
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 25.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
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.066
But a current signing key is available on our website 0.000
When the network is plugged 0.125
And Tor is ready 20.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.348
After features/support/hooks.rb:326 1.290
After features/support/hooks.rb:100 0.000