Project Number Date
test_Tails_ISO_stable 4979 29 Jul 2024, 15:09

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:26.177 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:12.975
Before features/support/hooks.rb:269 0.006
Given a computer 0.257
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 32.206
When I start Tails from USB drive "old" with network unplugged 1:35.281
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 6.933
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.798
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:23.958
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 31.451
And I take note of which tps features are available 1.413
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.593
After features/support/hooks.rb:326 0.226
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.942
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.285
Then Tails is running from USB drive "old" 0.293
And all tps features are active 1.964
When I write some files expected to persist 1.579
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.376
And I shutdown Tails and wait for the computer to power off 4.287
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.023
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.209
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.230
And I log in to a new session 19.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.660
And I plug USB drive "to_upgrade" 2.344
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.078
Then the running Tails is installed on USB drive "to_upgrade" 22.923
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:326 6.967
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.108
Before features/support/hooks.rb:269 0.006
Given a computer 0.274
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.649
Then all tps features from the old Tails version are active 1.591
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.034
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.696
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:44.617
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.924
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.100
And Tor is ready 49.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.115
Given I shutdown Tails and wait for the computer to power off 8.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.559
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.283
When the network is plugged 0.045
And Tor is ready 20.778
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.837
Given I shutdown Tails and wait for the computer to power off 4.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.313
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.027
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
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.382
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.042
And Tor is ready 17.922
Then the Upgrader considers the system as up-to-date 0.338
# 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 13.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.180
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.524
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 9.474
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
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.759
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 18.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.454
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.000