Project Number Date
test_Tails_ISO_stable 5026 13 Aug 2024, 17:53

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:19.846 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:19.992
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.231
When I start Tails from USB drive "old" with network unplugged 1:42.984
Then the boot device has safe access rights 3.357
And Tails is running from USB drive "old" 0.441
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.634
After features/support/hooks.rb:100 0.019
Tags: @product
2:23.829
Before features/support/hooks.rb:269 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:36.497
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 35.928
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.512
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.942
Before features/support/hooks.rb:269 0.006
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.350
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.108
When I write some files expected to persist 2.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.306
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.448
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.447
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.840
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.321
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.057
And I log in to a new session 21.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.254
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.146
Then the running Tails is installed on USB drive "to_upgrade" 21.671
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 3.569
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.059
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.724
Then all tps features from the old Tails version are active 1.663
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.052
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.644
After features/support/hooks.rb:326 0.589
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:7.476
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.661
And no SquashFS delta is installed 0.352
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.069
And Tor is ready 21.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.578
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.336
Given I shutdown Tails and wait for the computer to power off 8.961
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.297
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.047
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.273
When the network is plugged 0.077
And Tor is ready 20.992
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.789
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.349
Given I shutdown Tails and wait for the computer to power off 4.940
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.650
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.071
And Tor is ready 17.642
Then the Upgrader considers the system as up-to-date 0.313
# 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.290
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.224
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.711
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.792
After features/support/hooks.rb:326 0.911
After features/support/hooks.rb:100 0.000