Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 8 09 Dec 2024, 00: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 20:12.350 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:31.692
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 59.218
When I start Tails from USB drive "old" with network unplugged 1:26.535
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.288
After features/support/hooks.rb:326 7.012
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.733
Before features/support/hooks.rb:269 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:26.264
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.321
And I take note of which tps features are available 1.354
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.432
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.753
Before features/support/hooks.rb:269 0.009
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.493
Then Tails is running from USB drive "old" 0.829
And all tps features are active 2.103
When I write some files expected to persist 1.691
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.482
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.459
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.364
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.192
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.108
And I log in to a new session 20.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.625
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.271
Then the running Tails is installed on USB drive "to_upgrade" 23.843
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.937
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.023
Then all tps features from the old Tails version are active 1.550
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.208
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:5.010
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.802
And no SquashFS delta is installed 0.472
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.072
And Tor is ready 24.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.968
Given I shutdown Tails and wait for the computer to power off 8.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.470
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.285
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.255
When the network is plugged 0.080
And Tor is ready 47.842
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.934
Given I shutdown Tails and wait for the computer to power off 4.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.126
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.611
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.504
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.079
And Tor is ready 19.741
Then the Upgrader considers the system as up-to-date 0.287
# 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.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.115
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
42.030
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.957
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.824
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 22.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.182
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000