Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 46 26 Nov 2024, 07:18

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:50.233 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.824
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.768
When I start Tails from USB drive "old" with network unplugged 1:29.674
Then the boot device has safe access rights 2.996
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.778
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:22.675
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 30.885
And I take note of which tps features are available 1.597
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.007
Tags: @product
2:54.843
Before features/support/hooks.rb:269 0.009
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.563
Then Tails is running from USB drive "old" 0.976
And all tps features are active 2.161
When I write some files expected to persist 3.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.584
And I take note of which tps features are available 0.565
And I shutdown Tails and wait for the computer to power off 6.458
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.383
After features/support/hooks.rb:326 0.090
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.004
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.773
And I log in to a new session 20.168
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.610
And I plug USB drive "to_upgrade" 3.844
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.329
Then the running Tails is installed on USB drive "to_upgrade" 20.828
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 3.584
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.418
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.642
Then all tps features from the old Tails version are active 1.727
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.674
And all persistent directories from the old Tails version have safe access rights 2.398
After features/support/hooks.rb:326 0.956
After features/support/hooks.rb:100 0.009
6:28.698
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 12.309
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.073
And Tor is ready 22.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.895
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.024
Given I shutdown Tails and wait for the computer to power off 11.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.253
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.423
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.273
When the network is plugged 0.067
And Tor is ready 16.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.082
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.740
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.915
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.268
And the file system changes introduced in version 6.3~testoverlayfs are present 0.652
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.472
When the network is plugged 0.097
And Tor is ready 17.620
Then the Upgrader considers the system as up-to-date 10.781
# 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.750
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.002
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.019
35.666
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 10.386
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.785
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.391
After features/support/hooks.rb:326 0.930
After features/support/hooks.rb:100 0.000