Project Number Date
test_Tails_ISO_stable 5131 01 Oct 2024, 14:23

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 22:18.976 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:48.315
Before features/support/hooks.rb:269 0.006
Given a computer 0.293
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 57.267
When I start Tails from USB drive "old" with network unplugged 1:45.076
Then the boot device has safe access rights 3.404
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.727
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:23.573
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 38.562
And I take note of which tps features are available 1.730
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.386
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.623
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.215
Then Tails is running from USB drive "old" 1.300
And all tps features are active 5.026
When I write some files expected to persist 3.022
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.803
And I take note of which tps features are available 0.640
And I shutdown Tails and wait for the computer to power off 4.487
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.210
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.301
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 13.063
And I log in to a new session 21.212
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.719
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.993
Then the running Tails is installed on USB drive "to_upgrade" 28.216
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 0.311
After features/support/hooks.rb:326 3.650
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.683
Before features/support/hooks.rb:269 0.007
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.467
Then all tps features from the old Tails version are active 3.119
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 3.867
And the expected persistent files created with the old Tails version are present in the filesystem 1.655
And all persistent directories from the old Tails version have safe access rights 2.900
After features/support/hooks.rb:326 1.165
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:2.970
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.426
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
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.480
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.637
When the network is plugged 0.246
And Tor is ready 20.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.915
Given I shutdown Tails and wait for the computer to power off 8.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.799
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.400
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.456
When the network is plugged 0.107
And Tor is ready 49.769
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.766
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.710
Given I shutdown Tails and wait for the computer to power off 4.633
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.285
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.227
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.372
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.086
And Tor is ready 21.066
Then the Upgrader considers the system as up-to-date 0.352
# 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 16.890
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.463
After features/support/hooks.rb:326 1.076
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
48.354
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.872
But a current signing key is available on our website 0.000
When the network is plugged 0.947
And Tor is ready 23.566
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.221
After features/support/hooks.rb:326 0.790
After features/support/hooks.rb:100 0.000