Project Number Date
test_Tails_ISO_stable 5057 29 Aug 2024, 12: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:31.114 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:5.076
Before features/support/hooks.rb:269 0.003
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.028
When I start Tails from USB drive "old" with network unplugged 1:29.821
Then the boot device has safe access rights 2.883
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 6.984
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.815
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:23.081
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.007
And I take note of which tps features are available 2.010
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.369
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.707
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.374
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.879
When I write some files expected to persist 1.763
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.358
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.382
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.207
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.575
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.964
And I log in to a new session 17.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.197
Then the running Tails is installed on USB drive "to_upgrade" 18.213
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.440
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.648
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.816
Then all tps features from the old Tails version are active 1.450
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 2.964
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.372
After features/support/hooks.rb:326 1.033
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:13.882
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 11.333
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.060
And Tor is ready 18.269
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.849
Given I shutdown Tails and wait for the computer to power off 8.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.912
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.103
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.267
When the network is plugged 0.080
And Tor is ready 16.675
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.393
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.450
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.093
And Tor is ready 18.836
Then the Upgrader considers the system as up-to-date 0.315
# 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.678
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.994
After features/support/hooks.rb:326 1.112
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
33.409
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.817
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.366
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 16.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.094
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.000