Project Number Date
test_Tails_ISO_devel 3704 21 Feb 2025, 12:48

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:33.074 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:16.529
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.586
When I start Tails from USB drive "old" with network unplugged 1:38.346
Then the boot device has safe access rights 3.272
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.564
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.619
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:27.044
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 31.316
And I take note of which tps features are available 1.637
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.262
After features/support/hooks.rb:326 0.236
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.931
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.931
Then Tails is running from USB drive "old" 0.338
And all tps features are active 1.998
When I write some files expected to persist 2.125
# 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.349
And all persistent directories from the old Tails version have safe access rights 2.454
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.750
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.082
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.082
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.397
And I log in to a new session 18.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.590
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.457
Then the running Tails is installed on USB drive "to_upgrade" 22.250
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:326 2.245
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.958
Before features/support/hooks.rb:269 0.007
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.830
Then all tps features from the old Tails version are active 1.735
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.619
And all persistent directories from the old Tails version have safe access rights 2.554
After features/support/hooks.rb:326 0.841
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.540
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 13.966
And no SquashFS delta is installed 0.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.088
And Tor is ready 19.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.063
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.682
Given I shutdown Tails and wait for the computer to power off 8.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.890
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.286
When the network is plugged 0.065
And Tor is ready 17.704
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.149
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.213
Given I shutdown Tails and wait for the computer to power off 4.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.552
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.053
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.560
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.081
And Tor is ready 18.336
Then the Upgrader considers the system as up-to-date 0.369
# 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 16.324
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.412
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.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.514
After features/support/hooks.rb:326 0.946
After features/support/hooks.rb:100 0.000