Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 15 12 Dec 2024, 20:41

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 20:48.618 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:20.239
Before features/support/hooks.rb:269 0.004
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 32.129
When I start Tails from USB drive "old" with network unplugged 1:42.271
Then the boot device has safe access rights 3.412
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 3.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.924
Before features/support/hooks.rb:269 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:37.839
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 32.679
And I take note of which tps features are available 2.016
Then a Tails persistence partition exists on USB drive "old" 0.918
And I shutdown Tails and wait for the computer to power off 8.877
After features/support/hooks.rb:326 0.241
After features/support/hooks.rb:100 0.011
Tags: @product
3:12.561
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.712
Then Tails is running from USB drive "old" 0.419
And all tps features are active 3.077
When I write some files expected to persist 2.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.905
And I take note of which tps features are available 0.580
And I shutdown Tails and wait for the computer to power off 6.479
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.106
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.647
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.917
And I log in to a new session 21.037
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.469
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.814
Then the running Tails is installed on USB drive "to_upgrade" 22.351
And I unplug USB drive "to_upgrade" 0.434
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.306
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.452
Before features/support/hooks.rb:269 0.007
Given a computer 0.896
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.163
Then all tps features from the old Tails version are active 1.888
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.808
And all persistent directories from the old Tails version have safe access rights 2.658
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:2.310
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.640
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.070
And Tor is ready 24.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.396
Given I shutdown Tails and wait for the computer to power off 8.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.385
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.371
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.311
When the network is plugged 0.082
And Tor is ready 20.775
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.203
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.474
Given I shutdown Tails and wait for the computer to power off 6.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.868
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.069
And Tor is ready 19.085
Then the Upgrader considers the system as up-to-date 0.312
# 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.407
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.189
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.481
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.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 18.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.315
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.000