Project Number Date
test_Tails_ISO_stable 5027 13 Aug 2024, 18:31

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 20:6.319 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:13.128
Before features/support/hooks.rb:269 0.006
Given a computer 0.309
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.458
When I start Tails from USB drive "old" with network unplugged 1:35.171
Then the boot device has safe access rights 3.081
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.386
After features/support/hooks.rb:100 0.013
Tags: @product
2:11.288
Before features/support/hooks.rb:269 0.008
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login 1:27.052
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.306
And I take note of which tps features are available 1.595
Then a Tails persistence partition exists on USB drive "old" 1.008
And I shutdown Tails and wait for the computer to power off 8.679
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.404
Before features/support/hooks.rb:269 0.006
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.904
Then Tails is running from USB drive "old" 0.366
And all tps features are active 2.033
When I write some files expected to persist 1.765
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.106
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.697
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.519
And I log in to a new session 19.471
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.705
And I plug USB drive "to_upgrade" 2.459
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.650
Then the running Tails is installed on USB drive "to_upgrade" 18.459
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 6.961
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.676
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.328
Then all tps features from the old Tails version are active 2.230
And Tails is running from USB drive "to_upgrade" 0.620
And the boot device has safe access rights 4.971
And the expected persistent files created with the old Tails version are present in the filesystem 2.024
And all persistent directories from the old Tails version have safe access rights 3.284
After features/support/hooks.rb:326 1.131
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:50.828
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.752
And no SquashFS delta is installed 0.279
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
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.494
When the network is plugged 0.097
And Tor is ready 20.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.981
Given I shutdown Tails and wait for the computer to power off 8.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.109
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.777
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.322
When the network is plugged 0.894
And Tor is ready 20.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.087
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.124
Given I shutdown Tails and wait for the computer to power off 6.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.204
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.485
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.323
When the network is plugged 0.087
And Tor is ready 19.271
Then the Upgrader considers the system as up-to-date 0.436
# 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.089
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.195
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
45.296
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 15.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.878
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 20.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.804
After features/support/hooks.rb:326 1.448
After features/support/hooks.rb:100 0.000