Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 1 05 Dec 2024, 20:26

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:27.609 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:13.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.638
When I start Tails from USB drive "old" with network unplugged 1:34.223
Then the boot device has safe access rights 3.127
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.023
Tags: @product
2:9.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:25.805
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.022
And I take note of which tps features are available 1.560
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.251
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.828
Then Tails is running from USB drive "old" 0.803
And all tps features are active 1.829
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.686
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.702
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.400
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.817
And I log in to a new session 18.993
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.011
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.636
Then the running Tails is installed on USB drive "to_upgrade" 20.819
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 3.331
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.798
Then all tps features from the old Tails version are active 1.478
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.091
And the expected persistent files created with the old Tails version are present in the filesystem 1.665
And all persistent directories from the old Tails version have safe access rights 2.459
After features/support/hooks.rb:330 0.927
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:36.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.737
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.071
And Tor is ready 22.984
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 13.929
Given I shutdown Tails and wait for the computer to power off 9.088
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.915
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.134
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
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.282
# 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.244
When the network is plugged 0.081
And Tor is ready 21.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.794
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.617
Given I shutdown Tails and wait for the computer to power off 6.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.240
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.839
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.082
And Tor is ready 18.411
Then the Upgrader considers the system as up-to-date 0.366
# 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.058
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
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.889
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 23.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.653
After features/support/hooks.rb:330 0.667
After features/support/hooks.rb:100 0.000