Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 26 18 Dec 2024, 04:11

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:51.124 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:52.542
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.450
When I start Tails from USB drive "old" with network unplugged 1:18.887
Then the boot device has safe access rights 2.929
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.508
After features/support/hooks.rb:100 0.028
Tags: @product
2:6.144
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:25.230
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 31.660
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 6.510
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.983
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.714
Then Tails is running from USB drive "old" 0.513
And all tps features are active 1.972
When I write some files expected to persist 1.710
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.262
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.626
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.877
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.021
Before features/support/hooks.rb:269 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 10.077
And I log in to a new session 18.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.466
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.842
Then the running Tails is installed on USB drive "to_upgrade" 25.239
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:326 1.943
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.058
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.551
Then all tps features from the old Tails version are active 1.729
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.362
And all persistent directories from the old Tails version have safe access rights 2.393
After features/support/hooks.rb:326 0.996
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:36.270
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.195
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.065
And Tor is ready 23.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.456
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.420
Given I shutdown Tails and wait for the computer to power off 8.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.090
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.127
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.111
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.384
When the network is plugged 0.071
And Tor is ready 45.412
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.575
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.774
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.759
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.593
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.261
When the network is plugged 0.070
And Tor is ready 20.666
Then the Upgrader considers the system as up-to-date 0.351
# 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.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.958
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.103
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.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.720
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.512
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.000