Project Number Date
test_Tails_ISO_stable 4888 13 Jun 2024, 12:51

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 18:27.263 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:6.279
Before features/support/hooks.rb:269 0.008
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.738
When I start Tails from USB drive "old" with network unplugged 1:31.350
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:320 3.535
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.118
Before features/support/hooks.rb:269 0.008
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:19.366
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 33.756
And I take note of which tps features are available 1.484
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 8.230
After features/support/hooks.rb:320 0.197
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.196
Before features/support/hooks.rb:269 0.006
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.423
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.908
When I write some files expected to persist 1.647
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.704
And I shutdown Tails and wait for the computer to power off 4.586
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.239
After features/support/hooks.rb:320 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.613
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.226
And I log in to a new session 17.302
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.848
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.653
Then the running Tails is installed on USB drive "to_upgrade" 16.681
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:320 2.530
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.636
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.693
Then all tps features from the old Tails version are active 1.532
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.302
And the expected persistent files created with the old Tails version are present in the filesystem 1.366
And all persistent directories from the old Tails version have safe access rights 2.241
After features/support/hooks.rb:320 0.685
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:21.653
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 26.257
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.042
And Tor is ready 19.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.038
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.962
Given I shutdown Tails and wait for the computer to power off 8.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.688
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.332
When the network is plugged 0.040
And Tor is ready 18.192
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.989
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.782
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.092
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.033
And Tor is ready 18.131
Then the Upgrader considers the system as up-to-date 0.316
# 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.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.923
After features/support/hooks.rb:320 0.679
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.765
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 9.665
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 1.019
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 17.278
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.431
After features/support/hooks.rb:320 1.609
After features/support/hooks.rb:100 0.000