Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 11 10 Dec 2024, 00:42

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:57.717 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
1:56.925
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
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" 29.487
When I start Tails from USB drive "old" with network unplugged 1:22.067
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.089
Tags: @product
2:8.535
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:25.093
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.870
And I take note of which tps features are available 1.914
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.118
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.491
Then Tails is running from USB drive "old" 1.716
And all tps features are active 2.002
When I write some files expected to persist 1.760
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 4.321
And I take note of which tps features are available 0.607
And I shutdown Tails and wait for the computer to power off 4.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.091
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.336
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.933
And I log in to a new session 17.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.002
Then the running Tails is installed on USB drive "to_upgrade" 23.176
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 1.994
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.342
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.002
Then all tps features from the old Tails version are active 1.572
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:30.690
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.750
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.080
And Tor is ready 17.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.310
Given I shutdown Tails and wait for the computer to power off 8.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.737
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.260
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.306
When the network is plugged 0.065
And Tor is ready 19.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.688
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.736
Given I shutdown Tails and wait for the computer to power off 4.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.554
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.990
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.082
And Tor is ready 19.156
Then the Upgrader considers the system as up-to-date 10.808
# 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.928
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.051
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.767
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 12.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
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.088
And Tor is ready 18.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.542
After features/support/hooks.rb:326 0.755
After features/support/hooks.rb:100 0.000