Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 35 17 Nov 2024, 08:00

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:12.042 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:6.822
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.484
When I start Tails from USB drive "old" with network unplugged 1:29.967
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.379
Before features/support/hooks.rb:269 0.003
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:19.998
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 32.365
And I take note of which tps features are available 1.573
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.176
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.488
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.064
Then Tails is running from USB drive "old" 0.412
And all tps features are active 2.005
When I write some files expected to persist 1.745
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.528
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.185
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.770
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.165
And I log in to a new session 18.765
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.479
And I plug USB drive "to_upgrade" 3.859
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.118
Then the running Tails is installed on USB drive "to_upgrade" 17.968
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.010
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:53.968
Then all tps features from the old Tails version are active 1.675
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.845
And all persistent directories from the old Tails version have safe access rights 2.744
After features/support/hooks.rb:326 1.071
After features/support/hooks.rb:100 0.012
6:10.923
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 14.515
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.072
And Tor is ready 23.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.575
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.384
Given I shutdown Tails and wait for the computer to power off 10.695
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.913
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.513
When the network is plugged 0.074
And Tor is ready 16.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.825
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.708
Given I shutdown Tails and wait for the computer to power off 4.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.170
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.080
And Tor is ready 17.645
Then the Upgrader considers the system as up-to-date 0.290
# 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.052
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.055
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.019
35.649
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.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.866
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 18.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.918
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.000