Project Number Date
test_Tails_ISO_stable 5194 17 Oct 2024, 19:56

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:3.355 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:1.523
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.442
When I start Tails from USB drive "old" with network unplugged 1:26.303
Then the boot device has safe access rights 3.367
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.112
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.601
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.680
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:24.326
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 34.038
And I take note of which tps features are available 1.408
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.559
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.966
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.508
Then Tails is running from USB drive "old" 0.305
And all tps features are active 2.016
When I write some files expected to persist 1.641
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.268
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.195
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.957
And I log in to a new session 19.653
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.328
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.970
Then the running Tails is installed on USB drive "to_upgrade" 17.496
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.268
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.233
Then all tps features from the old Tails version are active 1.686
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.274
And the expected persistent files created with the old Tails version are present in the filesystem 1.870
And all persistent directories from the old Tails version have safe access rights 2.727
After features/support/hooks.rb:326 0.845
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:38.107
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 13.893
And no SquashFS delta is installed 0.533
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.817
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.095
And Tor is ready 21.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.560
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.694
Given I shutdown Tails and wait for the computer to power off 15.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.637
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.336
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.332
When the network is plugged 0.080
And Tor is ready 19.176
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.211
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.727
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.771
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.454
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.065
And Tor is ready 19.546
Then the Upgrader considers the system as up-to-date 0.363
# 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 13.940
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.997
After features/support/hooks.rb:326 0.755
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
33.614
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 9.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.779
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.884
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 16.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.242
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.000