Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 8 29 Oct 2024, 21:58

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:16.765 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:14.964
Before features/support/hooks.rb:269 0.003
Given a computer 0.145
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 29.878
When I start Tails from USB drive "old" with network unplugged 1:39.596
Then the boot device has safe access rights 3.196
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.496
After features/support/hooks.rb:100 0.005
Tags: @product
2:7.822
Before features/support/hooks.rb:269 0.002
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login 1:24.407
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 32.328
And I take note of which tps features are available 1.456
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.006
Tags: @product
2:54.666
Before features/support/hooks.rb:269 0.003
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.205
Then Tails is running from USB drive "old" 0.477
And all tps features are active 1.884
When I write some files expected to persist 1.996
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.759
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.722
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.006
Tags: @product
2:33.676
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.571
And I log in to a new session 20.418
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.438
And I plug USB drive "to_upgrade" 3.813
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.156
Then the running Tails is installed on USB drive "to_upgrade" 19.854
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.983
Before features/support/hooks.rb:269 0.004
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.664
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.241
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.006
6:45.345
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 13.378
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.065
And Tor is ready 22.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.038
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.288
Given I shutdown Tails and wait for the computer to power off 10.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.241
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.870
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# 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.434
When the network is plugged 0.070
And Tor is ready 46.315
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.729
Given I shutdown Tails and wait for the computer to power off 4.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.586
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.725
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.076
And Tor is ready 17.405
Then the Upgrader considers the system as up-to-date 0.322
# 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.952
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.090
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.013
33.306
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.755
But a current signing key is available on our website 0.000
When the network is plugged 0.133
And Tor is ready 15.176
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.349
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000