Project Number Date
test_Tails_ISO_stable 5112 24 Sep 2024, 09:09

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:43.396 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:20.940
Before features/support/hooks.rb:269 0.005
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.834
When I start Tails from USB drive "old" with network unplugged 1:42.131
Then the boot device has safe access rights 3.450
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:326 7.257
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.500
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:28.028
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 33.480
And I take note of which tps features are available 1.733
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.886
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.576
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.761
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.122
When I write some files expected to persist 1.695
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.668
And I take note of which tps features are available 1.659
And I shutdown Tails and wait for the computer to power off 4.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.075
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.293
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 12.813
And I log in to a new session 22.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.878
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.721
Then the running Tails is installed on USB drive "to_upgrade" 23.395
And I unplug USB drive "to_upgrade" 0.292
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.319
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.808
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.117
Then all tps features from the old Tails version are active 1.760
And Tails is running from USB drive "to_upgrade" 0.445
And the boot device has safe access rights 3.895
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.867
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:33.329
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.693
And no SquashFS delta is installed 0.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.070
And Tor is ready 23.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.580
Given I shutdown Tails and wait for the computer to power off 11.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.224
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.383
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.303
When the network is plugged 0.087
And Tor is ready 19.212
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.952
Given I shutdown Tails and wait for the computer to power off 4.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.830
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.064
And Tor is ready 19.454
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 15.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.297
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.946
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 11.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the signing key used by the Upgrader is outdated 0.980
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 17.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.330
After features/support/hooks.rb:326 1.040
After features/support/hooks.rb:100 0.000