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

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:24.140 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:22.220
Before features/support/hooks.rb:269 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.105
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 33.254
When I start Tails from USB drive "old" with network unplugged 1:43.406
Then the boot device has safe access rights 3.193
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 7.268
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.186
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 1:28.765
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.381
And I take note of which tps features are available 1.387
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.306
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.825
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.693
Then Tails is running from USB drive "old" 1.261
And all tps features are active 1.913
When I write some files expected to persist 2.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 3.587
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.356
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.153
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 10.174
And I log in to a new session 18.534
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.712
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.307
Then the running Tails is installed on USB drive "to_upgrade" 21.603
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 2.931
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.820
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.514
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.271
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.308
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.437
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.877
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.064
And Tor is ready 19.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.279
Given I shutdown Tails and wait for the computer to power off 8.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.429
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.594
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.069
# 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.332
When the network is plugged 0.076
And Tor is ready 19.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.284
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.112
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.205
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.963
And the file system changes introduced in version 6.3~testoverlayfs are present 0.696
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.418
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.081
And Tor is ready 18.670
Then the Upgrader considers the system as up-to-date 0.325
# 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.527
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:326 1.106
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.496
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 9.757
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 20.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.101
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.000