Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 2 25 Oct 2024, 06:52

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 17:58.652 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:1.828
Before features/support/hooks.rb:269 0.002
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 30.017
When I start Tails from USB drive "old" with network unplugged 1:26.646
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.502
After features/support/hooks.rb:100 0.049
Tags: @product
1:58.561
Before features/support/hooks.rb:269 0.003
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:18.492
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 30.935
And I take note of which tps features are available 1.448
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 6.437
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.006
Tags: @product
2:47.197
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:11.695
Then Tails is running from USB drive "old" 0.289
And all tps features are active 2.131
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.205
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 4.264
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.772
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.006
Tags: @product
2:30.218
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.141
And I log in to a new session 21.317
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.423
And I plug USB drive "to_upgrade" 3.934
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.395
Then the running Tails is installed on USB drive "to_upgrade" 20.605
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.925
After features/support/hooks.rb:100 0.000
Tags: @product
2:0.326
Before features/support/hooks.rb:269 0.003
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.994
Then all tps features from the old Tails version are active 1.719
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.748
And the expected persistent files created with the old Tails version are present in the filesystem 1.218
And all persistent directories from the old Tails version have safe access rights 2.193
After features/support/hooks.rb:326 0.898
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:4.884
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 11.738
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.452
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.064
And Tor is ready 26.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.261
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.207
Given I shutdown Tails and wait for the computer to power off 8.784
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.905
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.220
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.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.251
When the network is plugged 0.064
And Tor is ready 16.457
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.489
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.132
Given I shutdown Tails and wait for the computer to power off 4.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.682
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.971
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.066
And Tor is ready 17.130
Then the Upgrader considers the system as up-to-date 0.279
# 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.506
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.191
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
35.635
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.238
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 1.109
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.538
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.022
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.000