Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 39 20 Nov 2024, 07:09

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:36.575 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:2.863
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.979
When I start Tails from USB drive "old" with network unplugged 1:26.750
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.565
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.370
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:18.871
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.399
And I take note of which tps features are available 1.457
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.301
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.649
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.417
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.936
When I write some files expected to persist 2.003
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.313
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.054
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.988
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.940
And I log in to a new session 20.550
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.614
And I plug USB drive "to_upgrade" 2.859
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.660
Then the running Tails is installed on USB drive "to_upgrade" 20.949
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.545
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.836
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.520
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.498
And the expected persistent files created with the old Tails version are present in the filesystem 1.332
And all persistent directories from the old Tails version have safe access rights 2.368
After features/support/hooks.rb:326 1.043
After features/support/hooks.rb:100 0.008
6:34.777
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.703
And no SquashFS delta is installed 0.105
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.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.528
When the network is plugged 0.060
And Tor is ready 20.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.234
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.566
Given I shutdown Tails and wait for the computer to power off 10.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.176
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.469
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.423
When the network is plugged 0.099
And Tor is ready 49.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.567
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.273
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.076
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.071
And Tor is ready 18.889
Then the Upgrader considers the system as up-to-date 0.317
# 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.025
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.970
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.016
34.088
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.879
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.747
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 16.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.412
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.000