Project Number Date
test_Tails_ISO_stable 4873 04 Jun 2024, 21:15

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:40.057 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
1:58.684
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.209
When I start Tails from USB drive "old" with network unplugged 1:22.167
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:315 3.523
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.308
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:18.467
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 34.760
And I take note of which tps features are available 1.455
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.286
After features/support/hooks.rb:315 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.754
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.166
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.746
When I write some files expected to persist 2.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.384
And I shutdown Tails and wait for the computer to power off 4.482
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.255
After features/support/hooks.rb:315 0.114
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.470
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 10.408
And I log in to a new session 17.609
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.403
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.664
Then the running Tails is installed on USB drive "to_upgrade" 16.490
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:315 2.963
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.173
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.474
Then all tps features from the old Tails version are active 1.555
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.844
And the expected persistent files created with the old Tails version are present in the filesystem 1.531
And all persistent directories from the old Tails version have safe access rights 2.242
After features/support/hooks.rb:315 0.713
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.893
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.252
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.043
And Tor is ready 20.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.568
Given I shutdown Tails and wait for the computer to power off 8.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.323
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.907
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.361
When the network is plugged 0.051
And Tor is ready 20.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.249
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.540
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.760
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.876
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.056
And Tor is ready 46.288
Then the Upgrader considers the system as up-to-date 0.313
# 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 13.335
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.856
After features/support/hooks.rb:315 0.887
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.772
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.326
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 1.087
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 18.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.499
After features/support/hooks.rb:315 0.633
After features/support/hooks.rb:100 0.000