Project Number Date
test_Tails_ISO_stable 4858 28 May 2024, 22:21

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:30.637 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.321
Before features/support/hooks.rb:259 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.028
When I start Tails from USB drive "old" with network unplugged 1:32.385
Then the boot device has safe access rights 2.653
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:305 3.478
After features/support/hooks.rb:89 0.009
Tags: @product
2:8.081
Before features/support/hooks.rb:259 0.006
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:23.017
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 33.950
And I take note of which tps features are available 1.497
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.334
After features/support/hooks.rb:305 0.218
After features/support/hooks.rb:89 0.009
Tags: @product
2:51.263
Before features/support/hooks.rb:259 0.007
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.676
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.027
When I write some files expected to persist 1.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.625
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.111
After features/support/hooks.rb:305 0.150
After features/support/hooks.rb:89 0.010
Tags: @product
2:24.613
Before features/support/hooks.rb:259 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 11.191
And I log in to a new session 18.614
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.358
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.135
Then the running Tails is installed on USB drive "to_upgrade" 17.466
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:305 2.004
After features/support/hooks.rb:89 0.000
Tags: @product
2:6.476
Before features/support/hooks.rb:259 0.007
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.893
Then all tps features from the old Tails version are active 1.409
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.002
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.215
After features/support/hooks.rb:305 0.707
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:19.771
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.343
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.043
And Tor is ready 18.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.545
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.418
Given I shutdown Tails and wait for the computer to power off 8.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.886
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.991
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.372
When the network is plugged 0.041
And Tor is ready 20.976
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.103
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.183
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.857
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.048
And Tor is ready 19.785
Then the Upgrader considers the system as up-to-date 0.306
# 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.576
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.898
After features/support/hooks.rb:305 0.779
After features/support/hooks.rb:89 0.022
Tags: @product @automatic_upgrade
32.109
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.699
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.577
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 16.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.071
After features/support/hooks.rb:305 1.384
After features/support/hooks.rb:89 0.000