Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 25 18 Dec 2024, 00:13

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.957 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:16.607
Before features/support/hooks.rb:269 0.008
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.691
When I start Tails from USB drive "old" with network unplugged 1:40.329
Then the boot device has safe access rights 3.241
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.625
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.671
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:22.842
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 30.557
And I take note of which tps features are available 2.182
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.698
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.498
Before features/support/hooks.rb:269 0.005
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.543
Then Tails is running from USB drive "old" 0.858
And all tps features are active 2.762
When I write some files expected to persist 2.570
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.826
And I take note of which tps features are available 0.527
And I shutdown Tails and wait for the computer to power off 4.435
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.082
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.009
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 9.623
And I log in to a new session 20.029
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.952
Then the running Tails is installed on USB drive "to_upgrade" 20.865
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.572
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.832
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.188
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:31.754
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 15.825
And no SquashFS delta is installed 0.243
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.722
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.086
And Tor is ready 22.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.573
Given I shutdown Tails and wait for the computer to power off 10.980
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.507
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.287
When the network is plugged 0.122
And Tor is ready 19.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.113
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.589
Given I shutdown Tails and wait for the computer to power off 4.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.836
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.652
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.090
And Tor is ready 18.718
Then the Upgrader considers the system as up-to-date 0.295
# 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.452
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:326 0.993
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
41.582
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 10.743
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.989
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 22.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.514
After features/support/hooks.rb:326 1.169
After features/support/hooks.rb:100 0.000