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

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:50.922 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:8.512
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.365
When I start Tails from USB drive "old" with network unplugged 1:31.711
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 7.552
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:22.082
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 31.983
And I take note of which tps features are available 1.468
Then a Tails persistence partition exists on USB drive "old" 0.939
And I shutdown Tails and wait for the computer to power off 8.359
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.835
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.693
Then Tails is running from USB drive "old" 0.852
And all tps features are active 1.907
When I write some files expected to persist 3.093
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 3.113
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.424
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.470
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.964
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.238
And I log in to a new session 18.884
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.878
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.987
Then the running Tails is installed on USB drive "to_upgrade" 23.053
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 1.847
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.016
Before features/support/hooks.rb:269 0.006
Given a computer 0.523
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.655
Then all tps features from the old Tails version are active 2.855
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.599
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.013
7:19.225
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 12.013
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.061
And Tor is ready 50.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.601
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.884
Given I shutdown Tails and wait for the computer to power off 8.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.959
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.407
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.332
When the network is plugged 0.072
And Tor is ready 46.729
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.649
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.971
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.284
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.611
And only the 6.3~testoverlayfs SquashFS delta is installed 0.120
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.076
And Tor is ready 18.576
Then the Upgrader considers the system as up-to-date 0.344
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.041
After features/support/hooks.rb:326 1.030
After features/support/hooks.rb:100 0.017
37.965
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 9.773
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.777
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 20.189
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.683
After features/support/hooks.rb:326 0.860
After features/support/hooks.rb:100 0.000