Project Number Date
test_Tails_ISO_stable 5161 09 Oct 2024, 08:35

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:15.389 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:8.097
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.147
When I start Tails from USB drive "old" with network unplugged 1:32.385
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.535
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:21.854
Then Tails is running from USB drive "old" 0.417
And I create a persistent partition 32.439
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 6.298
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.440
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.430
Then Tails is running from USB drive "old" 0.423
And all tps features are active 2.011
When I write some files expected to persist 1.916
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.548
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.525
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.068
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.943
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.676
And I log in to a new session 22.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.754
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.517
Then the running Tails is installed on USB drive "to_upgrade" 24.611
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 2.469
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.907
Before features/support/hooks.rb:269 0.006
Given a computer 0.312
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.229
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.553
And all persistent directories from the old Tails version have safe access rights 2.378
After features/support/hooks.rb:326 0.652
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:42.196
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 40.176
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.387
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.116
And Tor is ready 20.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.761
Given I shutdown Tails and wait for the computer to power off 10.765
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.697
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.299
When the network is plugged 0.084
And Tor is ready 19.207
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.966
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.627
Given I shutdown Tails and wait for the computer to power off 4.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.862
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.071
And Tor is ready 17.883
Then the Upgrader considers the system as up-to-date 0.329
# 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.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.011
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.269
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 11.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 1.424
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.121
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000