Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 12 11 Dec 2024, 01:06

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:35.388 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:59.089
Before features/support/hooks.rb:269 0.005
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 34.338
When I start Tails from USB drive "old" with network unplugged 1:18.966
Then the boot device has safe access rights 3.346
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.673
After features/support/hooks.rb:100 0.036
Tags: @product
2:14.501
Before features/support/hooks.rb:269 0.003
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:27.004
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 35.903
And I take note of which tps features are available 1.698
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.535
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.993
Then Tails is running from USB drive "old" 0.514
And all tps features are active 1.995
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.832
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.605
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.179
And I log in to a new session 20.648
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.348
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.369
Then the running Tails is installed on USB drive "to_upgrade" 24.156
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.066
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.960
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.121
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.526
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.663
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.722
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.070
And Tor is ready 20.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.749
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.015
Given I shutdown Tails and wait for the computer to power off 8.742
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.848
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.317
When the network is plugged 0.070
And Tor is ready 19.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.622
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.032
Given I shutdown Tails and wait for the computer to power off 4.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.605
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.350
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.072
And Tor is ready 20.315
Then the Upgrader considers the system as up-to-date 0.306
# 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.743
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.072
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.033
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.241
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.784
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.419
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000