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

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:25.410 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
1:55.235
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.175
When I start Tails from USB drive "old" with network unplugged 1:21.129
Then the boot device has safe access rights 2.714
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.469
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.187
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:22.448
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 30.476
And I take note of which tps features are available 1.364
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.598
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.192
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 with persistence enabled 2:12.786
Then Tails is running from USB drive "old" 0.353
And all tps features are active 1.994
When I write some files expected to persist 1.930
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.378
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.248
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.194
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.864
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 11.278
And I log in to a new session 20.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.567
And I plug USB drive "to_upgrade" 4.196
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.808
Then the running Tails is installed on USB drive "to_upgrade" 18.646
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.927
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.560
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.970
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.515
And the expected persistent files created with the old Tails version are present in the filesystem 1.608
And all persistent directories from the old Tails version have safe access rights 2.249
After features/support/hooks.rb:326 1.058
After features/support/hooks.rb:100 0.008
6:23.646
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 12.343
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.116
And Tor is ready 19.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.681
Given I shutdown Tails and wait for the computer to power off 8.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.056
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.362
When the network is plugged 0.087
And Tor is ready 18.883
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.137
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.705
Given I shutdown Tails and wait for the computer to power off 4.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.589
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.079
And Tor is ready 16.871
Then the Upgrader considers the system as up-to-date 10.798
# 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.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.023
36.723
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 10.255
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.885
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.334
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.794
After features/support/hooks.rb:326 0.976
After features/support/hooks.rb:100 0.000