Project Number Date
test_Tails_ISO_devel 3701 19 Feb 2025, 15:13

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:23.795 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
1:59.975
Before features/support/hooks.rb:269 0.006
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.639
When I start Tails from USB drive "old" with network unplugged 1:21.868
Then the boot device has safe access rights 3.160
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.511
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.785
Before features/support/hooks.rb:269 0.007
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:29.819
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 33.417
And I take note of which tps features are available 1.568
Then a Tails persistence partition exists on USB drive "old" 0.894
And I shutdown Tails and wait for the computer to power off 8.499
After features/support/hooks.rb:326 0.251
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.483
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.382
Then Tails is running from USB drive "old" 0.697
And all tps features are active 2.075
When I write some files expected to persist 2.938
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.919
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.855
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.356
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 10.777
And I log in to a new session 18.285
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.593
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.607
Then the running Tails is installed on USB drive "to_upgrade" 19.244
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.350
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.123
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.842
Then all tps features from the old Tails version are active 1.858
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.651
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:58.012
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 11.627
And no SquashFS delta is installed 0.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.063
And Tor is ready 48.419
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.644
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.606
Given I shutdown Tails and wait for the computer to power off 8.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.217
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.382
And the file system changes introduced in version 6.2~testoverlayfs are present 0.404
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.283
When the network is plugged 0.103
And Tor is ready 20.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.882
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.856
Given I shutdown Tails and wait for the computer to power off 4.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.284
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.076
And Tor is ready 20.044
Then the Upgrader considers the system as up-to-date 0.313
# 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.596
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.051
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.057
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.811
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.094
After features/support/hooks.rb:326 0.973
After features/support/hooks.rb:100 0.000