Project Number Date
test_Tails_ISO_stable 4933 11 Jul 2024, 21:52

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:53.884 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.998
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.992
When I start Tails from USB drive "old" with network unplugged 1:36.616
Then the boot device has safe access rights 3.081
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 6.805
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.198
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:30.030
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 32.750
And I take note of which tps features are available 1.659
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 6.425
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.914
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.763
Then Tails is running from USB drive "old" 0.324
And all tps features are active 1.927
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.414
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.067
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.267
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 12.014
And I log in to a new session 18.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.494
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.939
Then the running Tails is installed on USB drive "to_upgrade" 21.944
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 3.553
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.218
Before features/support/hooks.rb:269 0.005
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.070
Then all tps features from the old Tails version are active 1.633
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.489
And the expected persistent files created with the old Tails version are present in the filesystem 2.035
And all persistent directories from the old Tails version have safe access rights 2.417
After features/support/hooks.rb:326 1.162
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:14.809
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.249
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.036
And Tor is ready 17.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.275
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.166
Given I shutdown Tails and wait for the computer to power off 8.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.695
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.290
When the network is plugged 0.045
And Tor is ready 22.213
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.691
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.959
Given I shutdown Tails and wait for the computer to power off 4.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.347
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.054
And Tor is ready 19.485
Then the Upgrader considers the system as up-to-date 0.355
# 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.074
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.053
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.476
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 10.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.889
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 18.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.260
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.000