Project Number Date
test_Tails_ISO_stable 4875 05 Jun 2024, 20:00

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.713 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:3.273
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.431
When I start Tails from USB drive "old" with network unplugged 1:25.569
Then the boot device has safe access rights 2.971
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:315 3.590
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.181
Before features/support/hooks.rb:269 0.006
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:22.367
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 38.365
And I take note of which tps features are available 1.322
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 8.585
After features/support/hooks.rb:315 0.199
After features/support/hooks.rb:100 0.041
Tags: @product
2:56.774
Before features/support/hooks.rb:269 0.008
Given a computer 0.672
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.817
Then Tails is running from USB drive "old" 0.380
And all tps features are active 1.951
When I write some files expected to persist 1.815
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.500
And I take note of which tps features are available 0.402
And I shutdown Tails and wait for the computer to power off 4.238
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.376
After features/support/hooks.rb:315 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.824
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.637
And I log in to a new session 17.240
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.791
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.569
Then the running Tails is installed on USB drive "to_upgrade" 18.692
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:315 0.807
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.226
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.280
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.048
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.245
After features/support/hooks.rb:315 0.711
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.209
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 10.547
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.033
And Tor is ready 18.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.877
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.509
Given I shutdown Tails and wait for the computer to power off 8.505
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.265
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.047
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.402
When the network is plugged 0.039
And Tor is ready 46.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.609
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.230
Given I shutdown Tails and wait for the computer to power off 4.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.109
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.382
And Tor is ready 16.316
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 13.524
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.864
After features/support/hooks.rb:315 0.659
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.223
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 9.525
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.935
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 19.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.349
After features/support/hooks.rb:315 0.675
After features/support/hooks.rb:100 0.000