Project Number Date
test_Tails_ISO_stable 5208 21 Oct 2024, 17:36

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 22:3.245 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:32.349
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.839
When I start Tails from USB drive "old" with network unplugged 1:54.875
Then the boot device has safe access rights 3.293
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.738
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.982
Before features/support/hooks.rb:269 0.004
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:27.990
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 33.333
And I take note of which tps features are available 1.544
Then a Tails persistence partition exists on USB drive "old" 0.946
And I shutdown Tails and wait for the computer to power off 8.557
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.920
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.486
Then Tails is running from USB drive "old" 0.872
And all tps features are active 2.153
When I write some files expected to persist 1.943
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.417
And all persistence configuration files have safe access rights 0.551
And all persistent directories from the old Tails version have safe access rights 3.606
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.535
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.656
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.585
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.290
And I log in to a new session 21.565
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.578
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.337
Then the running Tails is installed on USB drive "to_upgrade" 22.884
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.172
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.694
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.613
Then all tps features from the old Tails version are active 2.657
And Tails is running from USB drive "to_upgrade" 0.552
And the boot device has safe access rights 4.645
And the expected persistent files created with the old Tails version are present in the filesystem 1.874
And all persistent directories from the old Tails version have safe access rights 3.119
After features/support/hooks.rb:326 0.886
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
8:17.612
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 19.304
And no SquashFS delta is installed 0.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.626
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.678
When the network is plugged 0.097
And Tor is ready 20.885
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.622
Given I shutdown Tails and wait for the computer to power off 12.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.565
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.935
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.083
And Tor is ready 22.045
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.314
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.340
Given I shutdown Tails and wait for the computer to power off 1:7.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.847
Then Tails is running version 6.3~testoverlayfs 0.037
And all tps features are active 2.641
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.106
# 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.378
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.412
When the network is plugged 0.112
And Tor is ready 20.518
Then the Upgrader considers the system as up-to-date 0.396
# 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.239
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.450
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
40.100
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 14.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 1.080
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 16.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.449
After features/support/hooks.rb:326 1.335
After features/support/hooks.rb:100 0.000