Project Number Date
test_Tails_ISO_stable 5054 28 Aug 2024, 12:12

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:49.915 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:5.443
Before features/support/hooks.rb:269 0.005
Given a computer 1.002
And I create a 7200 MiB disk named "old" 0.316
And I plug USB drive "old" 1.252
And I write an old version of the Tails USB image to disk "old" 30.219
When I start Tails from USB drive "old" with network unplugged 1:28.479
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:326 3.568
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.885
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:29.997
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 30.395
And I take note of which tps features are available 1.982
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.162
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.751
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.291
Then Tails is running from USB drive "old" 0.342
And all tps features are active 2.068
When I write some files expected to persist 1.836
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
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.506
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.195
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.306
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.191
And I log in to a new session 20.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.867
And I plug USB drive "to_upgrade" 2.363
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.360
Then the running Tails is installed on USB drive "to_upgrade" 17.970
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.269
After features/support/hooks.rb:326 3.433
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.614
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.246
Then all tps features from the old Tails version are active 1.524
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.013
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.710
After features/support/hooks.rb:326 0.626
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.744
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 25.665
And no SquashFS delta is installed 0.901
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.061
And Tor is ready 19.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.590
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.032
Given I shutdown Tails and wait for the computer to power off 8.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.991
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.976
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.263
When the network is plugged 0.061
And Tor is ready 21.590
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.081
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.841
Given I shutdown Tails and wait for the computer to power off 4.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.592
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.067
And Tor is ready 17.173
Then the Upgrader considers the system as up-to-date 0.329
# 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.033
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.884
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.169
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.595
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.808
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.231
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.000