Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 19 04 Nov 2024, 16:49

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:20.269 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.085
Before features/support/hooks.rb:269 0.003
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.434
When I start Tails from USB drive "old" with network unplugged 1:37.968
Then the boot device has safe access rights 3.311
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 7.001
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.647
Before features/support/hooks.rb:269 0.003
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 1:28.668
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 31.997
And I take note of which tps features are available 1.865
Then a Tails persistence partition exists on USB drive "old" 0.907
And I shutdown Tails and wait for the computer to power off 8.687
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.005
Tags: @product
2:56.125
Before features/support/hooks.rb:269 0.002
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.078
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.164
When I write some files expected to persist 1.845
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.341
And all persistence configuration files have safe access rights 0.723
And all persistent directories from the old Tails version have safe access rights 2.808
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.434
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.590
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.006
Tags: @product
2:41.286
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 12.340
And I log in to a new session 23.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.873
And I plug USB drive "to_upgrade" 3.829
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.536
Then the running Tails is installed on USB drive "to_upgrade" 24.127
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 2.734
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.995
Before features/support/hooks.rb:269 0.003
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.401
Then all tps features from the old Tails version are active 2.132
And Tails is running from USB drive "to_upgrade" 0.710
And the boot device has safe access rights 3.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.414
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:326 1.266
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:33.507
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 14.309
And no SquashFS delta is installed 0.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.522
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.346
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.599
When the network is plugged 0.077
And Tor is ready 23.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.753
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.672
Given I shutdown Tails and wait for the computer to power off 10.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.630
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.392
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.419
When the network is plugged 0.068
And Tor is ready 20.632
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.964
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.970
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.655
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.422
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.534
When the network is plugged 0.068
And Tor is ready 18.934
Then the Upgrader considers the system as up-to-date 0.339
# 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.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.038
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
37.620
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 10.040
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.931
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.696
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000