Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 12 31 Oct 2024, 07:06

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 18:39.756 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:5.142
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.151
When I start Tails from USB drive "old" with network unplugged 1:29.775
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.520
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.486
Before features/support/hooks.rb:269 0.002
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:27.597
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 33.412
And I take note of which tps features are available 1.603
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.528
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.006
Tags: @product
2:49.607
Before features/support/hooks.rb:269 0.011
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.224
Then Tails is running from USB drive "old" 0.324
And all tps features are active 2.301
When I write some files expected to persist 1.868
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.291
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.110
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.236
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.006
Tags: @product
2:32.951
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 10.170
And I log in to a new session 21.733
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.728
And I plug USB drive "to_upgrade" 4.009
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.200
Then the running Tails is installed on USB drive "to_upgrade" 21.709
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.474
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.980
Before features/support/hooks.rb:269 0.003
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.823
Then all tps features from the old Tails version are active 1.869
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.596
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.711
After features/support/hooks.rb:326 0.957
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:16.141
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 12.330
And no SquashFS delta is installed 0.083
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.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.391
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.077
And Tor is ready 21.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.671
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.561
Given I shutdown Tails and wait for the computer to power off 10.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.254
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.166
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.268
When the network is plugged 0.081
And Tor is ready 20.153
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.638
Given I shutdown Tails and wait for the computer to power off 6.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.547
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.110
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.071
And Tor is ready 18.970
Then the Upgrader considers the system as up-to-date 0.289
# 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.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.048
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
36.447
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 12.346
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.777
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 17.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.010
After features/support/hooks.rb:326 0.755
After features/support/hooks.rb:100 0.000