Project Number Date
test_Tails_ISO_stable 4746 26 Mar 2024, 20:29

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 17:36.612 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:43.984
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 20.792
When I start Tails from USB drive "old" with network unplugged 1:17.511
Then the boot device has safe access rights 3.278
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:291 7.161
After features/support/hooks.rb:75 0.011
Tags: @product
2:10.933
Before features/support/hooks.rb:245 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:22.128
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 37.479
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.439
After features/support/hooks.rb:291 0.196
After features/support/hooks.rb:75 0.010
Tags: @product
2:33.154
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.780
Then Tails is running from USB drive "old" 0.401
And all tps features are active 1.999
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.557
And all persistent directories from the old Tails version have safe access rights 2.701
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.482
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.594
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.010
Tags: @product
2:24.523
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.205
And I log in to a new session 18.324
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.655
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.421
Then the running Tails is installed on USB drive "to_upgrade" 14.919
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:291 2.005
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.164
Before features/support/hooks.rb:245 0.009
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.626
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:291 0.747
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:8.040
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.166
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.063
And Tor is ready 16.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.520
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.967
Given I shutdown Tails and wait for the computer to power off 6.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.573
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.063
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.291
When the network is plugged 0.038
And Tor is ready 18.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.210
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.061
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.578
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.054
And Tor is ready 19.394
Then the Upgrader considers the system as up-to-date 0.223
# 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.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.850
After features/support/hooks.rb:291 0.778
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
32.810
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.987
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.472
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 16.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.316
After features/support/hooks.rb:291 0.703
After features/support/hooks.rb:75 0.000