Project Number Date
test_Tails_ISO_devel 3673 30 Jan 2025, 17:49

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:2.059 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:4.586
Before features/support/hooks.rb:269 0.003
Given a computer 0.278
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 30.194
When I start Tails from USB drive "old" with network unplugged 1:29.054
Then the boot device has safe access rights 2.991
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.730
After features/support/hooks.rb:100 0.006
Tags: @product
2:5.741
Before features/support/hooks.rb:269 0.002
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:22.846
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.993
And I take note of which tps features are available 1.390
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.176
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.006
Tags: @product
3:2.935
Before features/support/hooks.rb:269 0.003
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.135
Then Tails is running from USB drive "old" 1.383
And all tps features are active 2.262
When I write some files expected to persist 2.358
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.443
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.451
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.341
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.533
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.975
And I log in to a new session 20.188
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.398
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.574
Then the running Tails is installed on USB drive "to_upgrade" 20.589
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.557
Before features/support/hooks.rb:269 0.003
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.482
Then all tps features from the old Tails version are active 1.561
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.066
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.584
After features/support/hooks.rb:326 0.850
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:23.014
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 12.099
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.091
And Tor is ready 22.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.820
Given I shutdown Tails and wait for the computer to power off 8.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.544
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.350
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.269
When the network is plugged 0.102
And Tor is ready 20.226
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.013
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.843
Given I shutdown Tails and wait for the computer to power off 4.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.465
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.897
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.089
And Tor is ready 17.630
Then the Upgrader considers the system as up-to-date 10.783
# 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.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.001
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.088
Tags: @product @automatic_upgrade
35.689
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 17.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.881
After features/support/hooks.rb:326 2.684
After features/support/hooks.rb:100 0.000