Project Number Date
test_Tails_ISO_stable 5233 30 Oct 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 20:31.561 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:37.163
Before features/support/hooks.rb:269 0.004
Given a computer 0.435
And I create a 7200 MiB disk named "old" 0.243
And I plug USB drive "old" 1.136
And I write an old version of the Tails USB image to disk "old" 38.715
When I start Tails from USB drive "old" with network unplugged 1:51.901
Then the boot device has safe access rights 3.501
And Tails is running from USB drive "old" 0.412
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:326 3.638
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.728
Before features/support/hooks.rb:269 0.004
Given a computer 0.746
And I start Tails from USB drive "old" with network unplugged and I login 1:31.544
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 37.026
And I take note of which tps features are available 1.623
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.631
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
2:58.118
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.011
Then Tails is running from USB drive "old" 0.406
And all tps features are active 3.113
When I write some files expected to persist 2.269
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.482
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.353
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.185
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.021
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.869
And I log in to a new session 19.060
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.571
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.958
Then the running Tails is installed on USB drive "to_upgrade" 21.751
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 1.975
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.130
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.151
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.705
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.521
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:56.265
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 14.108
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.071
And Tor is ready 24.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.933
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.126
Given I shutdown Tails and wait for the computer to power off 13.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.625
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# 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.318
When the network is plugged 0.073
And Tor is ready 21.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.349
Given I shutdown Tails and wait for the computer to power off 4.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.181
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.328
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.081
And Tor is ready 18.891
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 15.391
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.183
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.133
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 12.804
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.534
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.817
But a current signing key is available on our website 0.000
When the network is plugged 0.128
And Tor is ready 22.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.662
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000