Project Number Date
test_Tails_ISO_stable 5221 24 Oct 2024, 20:32

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 20:1.418 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:11.541
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 34.281
When I start Tails from USB drive "old" with network unplugged 1:31.559
Then the boot device has safe access rights 3.342
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.579
After features/support/hooks.rb:100 0.032
Tags: @product
2:13.771
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:26.105
Then Tails is running from USB drive "old" 0.406
And I create a persistent partition 35.683
And I take note of which tps features are available 1.547
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.994
After features/support/hooks.rb:326 0.211
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.574
Before features/support/hooks.rb:269 0.006
Given a computer 0.622
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.225
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.539
When I write some files expected to persist 1.698
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.522
And I take note of which tps features are available 0.520
And I shutdown Tails and wait for the computer to power off 4.337
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.072
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.146
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 11.164
And I log in to a new session 19.701
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.784
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.596
Then the running Tails is installed on USB drive "to_upgrade" 23.067
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.048
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.518
Before features/support/hooks.rb:269 0.025
Given a computer 0.810
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.684
Then all tps features from the old Tails version are active 1.857
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 4.288
And the expected persistent files created with the old Tails version are present in the filesystem 1.698
And all persistent directories from the old Tails version have safe access rights 2.783
After features/support/hooks.rb:326 1.307
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:54.940
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.586
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.089
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.694
When the network is plugged 1.410
And Tor is ready 21.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.644
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.537
Given I shutdown Tails and wait for the computer to power off 11.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.828
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.348
When the network is plugged 0.066
And Tor is ready 21.229
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.006
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.096
Given I shutdown Tails and wait for the computer to power off 6.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.611
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.619
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.431
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.071
And Tor is ready 20.664
Then the Upgrader considers the system as up-to-date 0.343
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.088
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.924
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.562
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.648
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.945
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.352
After features/support/hooks.rb:326 2.208
After features/support/hooks.rb:100 0.000