Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 7 29 Oct 2024, 16:37

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:25.056 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:14.692
Before features/support/hooks.rb:269 0.002
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.755
When I start Tails from USB drive "old" with network unplugged 1:38.430
Then the boot device has safe access rights 3.219
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.517
After features/support/hooks.rb:100 0.023
Tags: @product
2:16.511
Before features/support/hooks.rb:269 0.003
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:32.787
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.009
And I take note of which tps features are available 1.921
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 8.497
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.006
Tags: @product
2:51.626
Before features/support/hooks.rb:269 0.003
Given a computer 0.522
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.477
Then Tails is running from USB drive "old" 0.730
And all tps features are active 2.060
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 2.727
And I take note of which tps features are available 0.402
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.799
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.165
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.482
And I log in to a new session 24.277
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.018
And I plug USB drive "to_upgrade" 2.690
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.462
Then the running Tails is installed on USB drive "to_upgrade" 22.792
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 3.580
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.839
Before features/support/hooks.rb:269 0.003
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.060
Then all tps features from the old Tails version are active 1.818
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.563
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:326 1.100
After features/support/hooks.rb:100 0.006
6:15.500
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 12.266
And no SquashFS delta is installed 0.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.072
And Tor is ready 20.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.597
Given I shutdown Tails and wait for the computer to power off 8.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.364
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.431
# 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.411
When the network is plugged 0.066
And Tor is ready 18.879
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.799
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.226
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.804
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.159
# 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.561
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.478
When the network is plugged 0.079
And Tor is ready 19.185
Then the Upgrader considers the system as up-to-date 0.334
# 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.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.205
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.014
59.720
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.516
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 46.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.610
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000