Project Number Date
test_Tails_ISO_stable 5107 21 Sep 2024, 12:19

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 18:20.557 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
1:59.774
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.720
When I start Tails from USB drive "old" with network unplugged 1:25.777
Then the boot device has safe access rights 3.020
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.520
After features/support/hooks.rb:100 0.036
Tags: @product
2:0.435
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:18.610
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 30.640
And I take note of which tps features are available 1.744
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.138
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.360
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.661
Then Tails is running from USB drive "old" 0.296
And all tps features are active 1.991
When I write some files expected to persist 1.520
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.368
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.252
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.025
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.604
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.385
And I log in to a new session 18.723
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.544
And I plug USB drive "to_upgrade" 2.355
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.311
Then the running Tails is installed on USB drive "to_upgrade" 17.859
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.232
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.206
Before features/support/hooks.rb:269 0.004
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.095
Then all tps features from the old Tails version are active 1.496
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.311
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.275
After features/support/hooks.rb:326 0.997
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:24.100
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.493
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.089
And Tor is ready 21.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.497
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.698
Given I shutdown Tails and wait for the computer to power off 8.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.040
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.267
When the network is plugged 0.064
And Tor is ready 16.757
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.257
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.434
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.559
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.895
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.274
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.074
And Tor is ready 16.787
Then the Upgrader considers the system as up-to-date 10.803
# 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.889
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.075
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 9.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.717
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.210
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000