Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 5 06 Dec 2024, 22:22

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 21:56.541 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:29.926
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 33.821
When I start Tails from USB drive "old" with network unplugged 1:50.003
Then the boot device has safe access rights 3.563
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.160
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:326 8.729
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.210
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:34.226
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 33.076
And I take note of which tps features are available 1.778
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.665
After features/support/hooks.rb:326 0.273
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.956
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.295
Then Tails is running from USB drive "old" 1.209
And all tps features are active 2.175
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 3.231
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.345
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.255
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.596
And I log in to a new session 20.464
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.506
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.320
Then the running Tails is installed on USB drive "to_upgrade" 25.296
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 7.156
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.172
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.972
Then all tps features from the old Tails version are active 1.847
And Tails is running from USB drive "to_upgrade" 0.413
And the boot device has safe access rights 3.406
And the expected persistent files created with the old Tails version are present in the filesystem 1.585
And all persistent directories from the old Tails version have safe access rights 2.723
After features/support/hooks.rb:326 1.007
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
8:15.490
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.854
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.388
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.077
And Tor is ready 22.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.750
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.112
Given I shutdown Tails and wait for the computer to power off 1:22.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.312
Then Tails is running version 6.2~testoverlayfs 0.418
And all tps features are active 2.797
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.371
# 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.336
When the network is plugged 0.072
And Tor is ready 47.551
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.715
Given I shutdown Tails and wait for the computer to power off 4.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.484
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.464
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
And only the 6.3~testoverlayfs SquashFS delta is installed 0.126
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.085
And Tor is ready 17.742
Then the Upgrader considers the system as up-to-date 0.335
# 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.120
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.196
After features/support/hooks.rb:326 1.048
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.527
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.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.564
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.129
And the signing key used by the Upgrader is outdated 0.895
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.026
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.000