Project Number Date
test_Tails_ISO_devel 3700 19 Feb 2025, 12: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 18:37.648 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.428
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.745
When I start Tails from USB drive "old" with network unplugged 1:25.464
Then the boot device has safe access rights 2.967
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.494
After features/support/hooks.rb:100 0.021
Tags: @product
2:8.062
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:25.398
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 31.830
And I take note of which tps features are available 1.247
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.250
After features/support/hooks.rb:326 0.274
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.100
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.178
Then Tails is running from USB drive "old" 0.309
And all tps features are active 2.156
When I write some files expected to persist 2.085
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.393
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.165
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.193
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.109
And I log in to a new session 18.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.509
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.139
Then the running Tails is installed on USB drive "to_upgrade" 22.897
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 6.739
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.047
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.080
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 2.965
And the expected persistent files created with the old Tails version are present in the filesystem 1.651
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.117
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 11.845
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.065
And Tor is ready 17.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.789
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.177
Given I shutdown Tails and wait for the computer to power off 8.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.729
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.105
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.317
When the network is plugged 0.076
And Tor is ready 20.225
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.138
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.347
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.669
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.068
And Tor is ready 16.920
Then the Upgrader considers the system as up-to-date 0.339
# 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.653
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.888
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.698
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 10.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.524
After features/support/hooks.rb:326 0.764
After features/support/hooks.rb:100 0.000