Project Number Date
test_Tails_ISO_stable 5437 01 Feb 2025, 12:43

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 19:4.296 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:5.991
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.543
When I start Tails from USB drive "old" with network unplugged 1:29.200
Then the boot device has safe access rights 2.938
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.035
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.891
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:35.773
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 36.221
And I take note of which tps features are available 1.383
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.147
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.007
Tags: @product
2:48.913
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.216
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.917
When I write some files expected to persist 1.897
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
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.608
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.435
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.136
After features/support/hooks.rb:326 0.095
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.594
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.942
And I log in to a new session 19.547
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.531
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.032
Then the running Tails is installed on USB drive "to_upgrade" 21.721
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 1.869
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.231
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.381
Then all tps features from the old Tails version are active 1.586
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.943
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.403
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.903
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.144
And no SquashFS delta is installed 0.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.799
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.180
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.185
And Tor is ready 21.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.669
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.737
Given I shutdown Tails and wait for the computer to power off 8.502
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.036
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.248
When the network is plugged 0.075
And Tor is ready 19.019
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.202
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.900
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.953
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.087
And Tor is ready 20.382
Then the Upgrader considers the system as up-to-date 0.294
# 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.457
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.769
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.288
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the signing key used by the Upgrader is outdated 0.179
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.142
After features/support/hooks.rb:326 1.104
After features/support/hooks.rb:100 0.000