Project Number Date
test_Tails_ISO_stable 5005 07 Aug 2024, 15:26

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 20:7.383 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:28.845
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.623
When I start Tails from USB drive "old" with network unplugged 1:51.673
Then the boot device has safe access rights 3.117
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.396
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.485
After features/support/hooks.rb:100 0.013
Tags: @product
2:9.145
Before features/support/hooks.rb:269 0.008
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:24.041
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.912
And I take note of which tps features are available 1.749
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 8.961
After features/support/hooks.rb:326 0.211
After features/support/hooks.rb:100 0.019
Tags: @product
2:58.595
Before features/support/hooks.rb:269 0.013
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.552
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.316
When I write some files expected to persist 1.874
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.631
And all persistent directories from the old Tails version have safe access rights 2.569
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.302
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.942
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.488
Before features/support/hooks.rb:269 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 10.429
And I log in to a new session 20.244
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.476
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.764
Then the running Tails is installed on USB drive "to_upgrade" 24.732
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:326 2.304
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.651
Before features/support/hooks.rb:269 0.014
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.359
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.875
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.607
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:57.824
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.336
And no SquashFS delta is installed 0.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.533
When the network is plugged 0.077
And Tor is ready 23.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.868
Given I shutdown Tails and wait for the computer to power off 8.830
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.271
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.455
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.287
When the network is plugged 0.064
And Tor is ready 22.997
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.199
Given I shutdown Tails and wait for the computer to power off 4.657
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.777
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.589
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.475
When the network is plugged 0.082
And Tor is ready 20.348
Then the Upgrader considers the system as up-to-date 0.365
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.205
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
36.832
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.603
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.826
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.399
After features/support/hooks.rb:326 1.142
After features/support/hooks.rb:100 0.000