Project Number Date
test_Tails_ISO_devel 3797 30 Apr 2025, 09:51

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 18:48.577 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:8.058
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 35.307
When I start Tails from USB drive "old" with network unplugged 1:27.217
Then the boot device has safe access rights 3.135
And Tails is running from USB drive "old" 0.386
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.968
After features/support/hooks.rb:100 0.012
Tags: @product
2:5.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:24.008
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 29.799
And I take note of which tps features are available 1.780
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.929
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.244
Then Tails is running from USB drive "old" 0.529
And all tps features are active 1.926
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.500
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.647
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.794
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.124
And I log in to a new session 19.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.572
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.563
Then the running Tails is installed on USB drive "to_upgrade" 19.382
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 1.060
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.333
Then all tps features from the old Tails version are active 1.676
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.471
And the expected persistent files created with the old Tails version are present in the filesystem 1.366
And all persistent directories from the old Tails version have safe access rights 2.221
After features/support/hooks.rb:330 1.731
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:19.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.881
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.070
And Tor is ready 22.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.818
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.936
Given I shutdown Tails and wait for the computer to power off 8.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.940
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.288
When the network is plugged 0.071
And Tor is ready 17.467
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.992
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.468
Given I shutdown Tails and wait for the computer to power off 6.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.305
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.906
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.428
When the network is plugged 0.069
And Tor is ready 17.003
Then the Upgrader considers the system as up-to-date 0.300
# 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.106
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.708
After features/support/hooks.rb:330 0.758
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.524
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 18.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.857
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.000