Project Number Date
test_Tails_ISO_stable 4877 07 Jun 2024, 12:41

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:15.691 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:1.004
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.966
When I start Tails from USB drive "old" with network unplugged 1:23.966
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:315 7.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.106
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.550
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 34.283
And I take note of which tps features are available 1.601
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.292
After features/support/hooks.rb:315 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.708
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.316
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.065
When I write some files expected to persist 1.570
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.737
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 4.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.119
After features/support/hooks.rb:315 0.089
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.107
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 9.742
And I log in to a new session 17.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.601
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.708
Then the running Tails is installed on USB drive "to_upgrade" 16.666
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:315 3.505
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.441
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.154
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.397
And the expected persistent files created with the old Tails version are present in the filesystem 1.458
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:315 0.704
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
6:11.976
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 11.037
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.045
And Tor is ready 16.994
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.678
Given I shutdown Tails and wait for the computer to power off 8.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.705
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.239
When the network is plugged 0.038
And Tor is ready 20.080
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.899
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.828
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.701
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.948
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.482
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.038
And Tor is ready 17.764
Then the Upgrader considers the system as up-to-date 0.317
# 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.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.039
After features/support/hooks.rb:315 0.747
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.347
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 9.417
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.008
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 17.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
After features/support/hooks.rb:315 0.887
After features/support/hooks.rb:100 0.000