Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 8 17 Nov 2024, 17:29

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 21:1.908 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:32.063
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 42.428
When I start Tails from USB drive "old" with network unplugged 1:43.472
Then the boot device has safe access rights 3.251
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.771
After features/support/hooks.rb:326 7.561
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.313
Before features/support/hooks.rb:269 0.005
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:24.853
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 34.114
And I take note of which tps features are available 1.575
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.346
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.350
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.264
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.146
When I write some files expected to persist 1.597
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.588
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 4.535
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.553
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.281
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 11.464
And I log in to a new session 22.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.834
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.322
Then the running Tails is installed on USB drive "to_upgrade" 23.694
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 7.451
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.562
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.759
Then all tps features from the old Tails version are active 1.851
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.529
And all persistent directories from the old Tails version have safe access rights 2.536
After features/support/hooks.rb:326 1.027
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:43.560
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.244
And no SquashFS delta is installed 0.305
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.463
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.064
And Tor is ready 19.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.223
Given I shutdown Tails and wait for the computer to power off 1:21.039
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.323
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.556
# 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.398
When the network is plugged 0.092
And Tor is ready 17.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.783
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.631
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.334
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.104
And Tor is ready 18.249
Then the Upgrader considers the system as up-to-date 0.341
# 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.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.144
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
39.776
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 10.500
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.827
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 21.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.758
After features/support/hooks.rb:326 0.647
After features/support/hooks.rb:100 0.000