Project Number Date
test_Tails_ISO_stable 4963 23 Jul 2024, 12:49

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.137 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:16.937
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.000
When I start Tails from USB drive "old" with network unplugged 1:42.704
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.517
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.159
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:20.606
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 31.200
And I take note of which tps features are available 1.442
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.650
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.022
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.360
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.241
When I write some files expected to persist 1.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.138
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.296
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.256
And I log in to a new session 18.276
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.386
And I plug USB drive "to_upgrade" 2.359
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.950
Then the running Tails is installed on USB drive "to_upgrade" 16.627
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 3.078
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.419
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.454
Then all tps features from the old Tails version are active 1.600
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.016
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:326 1.300
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.198
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.300
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.375
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.044
And Tor is ready 20.942
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.417
Given I shutdown Tails and wait for the computer to power off 8.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.367
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.261
When the network is plugged 0.044
And Tor is ready 18.527
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.177
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.076
Given I shutdown Tails and wait for the computer to power off 4.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.370
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.958
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.060
And Tor is ready 19.393
Then the Upgrader considers the system as up-to-date 0.360
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.133
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.077
Tags: @product @automatic_upgrade
35.102
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 10.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.746
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 17.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.589
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000