Project Number Date
test_Tails_ISO_stable 4844 16 May 2024, 13:03

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:10.619 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:7.427
Before features/support/hooks.rb:259 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.018
When I start Tails from USB drive "old" with network unplugged 1:30.821
Then the boot device has safe access rights 3.259
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:305 3.679
After features/support/hooks.rb:89 0.012
Tags: @product
2:11.976
Before features/support/hooks.rb:259 0.008
Given a computer 0.515
And I start Tails from USB drive "old" with network unplugged and I login 1:26.488
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 33.026
And I take note of which tps features are available 2.158
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.563
After features/support/hooks.rb:305 0.156
After features/support/hooks.rb:89 0.012
Tags: @product
2:55.289
Before features/support/hooks.rb:259 0.008
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.289
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.008
When I write some files expected to persist 1.608
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.524
And all persistent directories from the old Tails version have safe access rights 2.649
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 4.399
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.545
After features/support/hooks.rb:305 0.130
After features/support/hooks.rb:89 0.014
Tags: @product
2:35.073
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.551
And I log in to a new session 18.405
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.443
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.262
Then the running Tails is installed on USB drive "to_upgrade" 23.486
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:305 7.738
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.215
Before features/support/hooks.rb:259 0.010
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.597
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.650
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:305 0.630
After features/support/hooks.rb:89 0.015
6:23.596
Before features/support/hooks.rb:259 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.746
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.125
And Tor is ready 22.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.431
Given I shutdown Tails and wait for the computer to power off 8.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.088
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.369
And the file system changes introduced in version 6.2~testoverlayfs are present 0.467
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.320
When the network is plugged 0.034
And Tor is ready 19.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.335
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.025
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.989
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.035
And Tor is ready 17.711
Then the Upgrader considers the system as up-to-date 0.303
# 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.647
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:305 0.739
After features/support/hooks.rb:89 0.100
39.039
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 10.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.426
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 21.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.808
After features/support/hooks.rb:305 0.647
After features/support/hooks.rb:89 0.000