Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 15 01 Nov 2024, 07:13

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:47.136 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:8.710
Before features/support/hooks.rb:269 0.003
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 28.557
When I start Tails from USB drive "old" with network unplugged 1:35.098
Then the boot device has safe access rights 2.862
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.006
Tags: @product
2:3.339
Before features/support/hooks.rb:269 0.003
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:18.196
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 33.940
And I take note of which tps features are available 1.558
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.332
After features/support/hooks.rb:326 0.235
After features/support/hooks.rb:100 0.006
Tags: @product
2:54.776
Before features/support/hooks.rb:269 0.002
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.602
Then Tails is running from USB drive "old" 0.633
And all tps features are active 1.880
When I write some files expected to persist 1.528
# 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.339
And all persistent directories from the old Tails version have safe access rights 2.631
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.459
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.857
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.006
Tags: @product
2:33.688
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.760
And I log in to a new session 22.106
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.887
And I plug USB drive "to_upgrade" 4.110
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.390
Then the running Tails is installed on USB drive "to_upgrade" 19.995
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:326 3.078
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.445
Before features/support/hooks.rb:269 0.002
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.804
Then all tps features from the old Tails version are active 1.891
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.982
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:326 0.947
After features/support/hooks.rb:100 0.006
6:8.239
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 11.935
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.123
And Tor is ready 20.376
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.333
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.160
Given I shutdown Tails and wait for the computer to power off 10.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.353
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.070
And Tor is ready 17.910
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.807
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.310
Given I shutdown Tails and wait for the computer to power off 4.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.420
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.185
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.507
When the network is plugged 0.099
And Tor is ready 18.345
Then the Upgrader considers the system as up-to-date 0.309
# 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.679
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.958
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.011
56.935
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 9.619
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.690
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 45.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.550
After features/support/hooks.rb:326 0.634
After features/support/hooks.rb:100 0.000