Project Number Date
test_Tails_ISO_devel 3604 06 Dec 2024, 12:37

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 19:16.236 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:23.095
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 52.638
When I start Tails from USB drive "old" with network unplugged 1:25.225
Then the boot device has safe access rights 2.905
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 3.497
After features/support/hooks.rb:100 0.019
Tags: @product
2:6.005
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:22.291
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 32.477
And I take note of which tps features are available 1.446
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.419
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.476
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.632
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.994
When I write some files expected to persist 2.025
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.388
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.311
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.575
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 11.086
And I log in to a new session 20.198
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.697
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.578
Then the running Tails is installed on USB drive "to_upgrade" 19.167
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.032
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.201
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.242
Then all tps features from the old Tails version are active 1.610
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.009
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.449
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:35.822
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 12.313
And no SquashFS delta is installed 0.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.076
And Tor is ready 23.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.586
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.536
Given I shutdown Tails and wait for the computer to power off 10.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.306
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.049
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
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.291
# 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.311
When the network is plugged 0.071
And Tor is ready 20.020
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.327
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.211
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.946
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.075
And Tor is ready 19.117
Then the Upgrader considers the system as up-to-date 0.307
# 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.274
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.228
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.059
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 11.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.824
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 17.994
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.618
After features/support/hooks.rb:326 1.204
After features/support/hooks.rb:100 0.000