Project Number Date
test_Tails_ISO_stable 5303 29 Nov 2024, 08:41

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:3.255 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.146
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.098
When I start Tails from USB drive "old" with network unplugged 1:30.206
Then the boot device has safe access rights 3.388
And Tails is running from USB drive "old" 0.380
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:326 7.269
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.743
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:29.858
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.141
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 8.840
After features/support/hooks.rb:326 0.225
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.141
Before features/support/hooks.rb:269 0.004
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.000
Then Tails is running from USB drive "old" 1.023
And all tps features are active 2.091
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.306
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.307
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 4.202
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.036
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.466
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 11.660
And I log in to a new session 18.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.556
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.216
Then the running Tails is installed on USB drive "to_upgrade" 22.934
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.148
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.857
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.409
Then all tps features from the old Tails version are active 1.850
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.259
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.297
After features/support/hooks.rb:326 2.134
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.850
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 12.998
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.843
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.074
And Tor is ready 22.534
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.529
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.226
Given I shutdown Tails and wait for the computer to power off 10.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.451
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.279
When the network is plugged 0.062
And Tor is ready 19.044
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.541
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.551
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.934
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.956
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.074
And Tor is ready 18.682
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 14.927
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:326 0.653
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
41.051
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 12.474
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
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 0.921
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 20.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.434
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000