Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 1 24 Oct 2024, 21: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 19:55.557 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.821
Before features/support/hooks.rb:269 0.003
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.382
When I start Tails from USB drive "old" with network unplugged 1:50.635
Then the boot device has safe access rights 3.312
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.254
After features/support/hooks.rb:326 3.839
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.235
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:25.849
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 34.336
And I take note of which tps features are available 1.557
Then a Tails persistence partition exists on USB drive "old" 0.943
And I shutdown Tails and wait for the computer to power off 9.012
After features/support/hooks.rb:326 0.247
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.724
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.008
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.137
When I write some files expected to persist 1.974
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.340
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.404
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.371
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.038
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.005
Tags: @product
2:43.935
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.601
And I log in to a new session 27.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.142
And I plug USB drive "to_upgrade" 2.868
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.875
Then the running Tails is installed on USB drive "to_upgrade" 22.801
And I unplug USB drive "to_upgrade" 0.363
And I unplug USB drive "__internal" 0.303
After features/support/hooks.rb:326 3.600
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.548
Before features/support/hooks.rb:269 0.002
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.334
Then all tps features from the old Tails version are active 1.992
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.597
And all persistent directories from the old Tails version have safe access rights 2.634
After features/support/hooks.rb:326 1.225
After features/support/hooks.rb:100 0.006
6:39.609
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.860
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.065
And Tor is ready 23.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.843
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.496
Given I shutdown Tails and wait for the computer to power off 11.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.072
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 2.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.119
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.396
# 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.588
When the network is plugged 0.094
And Tor is ready 18.058
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.534
Given I shutdown Tails and wait for the computer to power off 4.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.730
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.386
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.069
And Tor is ready 17.087
Then the Upgrader considers the system as up-to-date 10.929
# 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 15.224
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.203
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.015
38.682
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.592
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.781
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.904
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.553
After features/support/hooks.rb:326 0.888
After features/support/hooks.rb:100 0.000