Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 9 29 Oct 2024, 22:34

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:26.443 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.745
Before features/support/hooks.rb:269 0.003
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.924
When I start Tails from USB drive "old" with network unplugged 1:31.622
Then the boot device has safe access rights 2.852
And Tails is running from USB drive "old" 0.393
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.541
After features/support/hooks.rb:100 0.006
Tags: @product
2:6.719
Before features/support/hooks.rb:269 0.003
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:23.598
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 32.258
And I take note of which tps features are available 1.485
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.105
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.006
Tags: @product
2:50.910
Before features/support/hooks.rb:269 0.002
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.541
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.141
When I write some files expected to persist 2.605
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.505
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.428
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.044
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.006
Tags: @product
2:48.287
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 24.684
And I log in to a new session 24.328
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.873
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.920
Then the running Tails is installed on USB drive "to_upgrade" 21.632
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.738
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.548
Before features/support/hooks.rb:269 0.003
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.519
Then all tps features from the old Tails version are active 1.842
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.800
And the expected persistent files created with the old Tails version are present in the filesystem 1.381
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:326 1.863
After features/support/hooks.rb:100 0.006
6:38.002
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.611
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.757
When the network is plugged 0.117
And Tor is ready 49.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.401
Given I shutdown Tails and wait for the computer to power off 10.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.595
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.424
# 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.379
When the network is plugged 0.064
And Tor is ready 16.265
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.837
Given I shutdown Tails and wait for the computer to power off 4.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.900
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.821
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.060
And Tor is ready 17.721
Then the Upgrader considers the system as up-to-date 0.327
# 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.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.011
35.228
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 9.587
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.967
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 19.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.990
After features/support/hooks.rb:326 0.844
After features/support/hooks.rb:100 0.000