Project Number Date
test_Tails_ISO_stable 5119 25 Sep 2024, 14:40

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:36.461 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:22.488
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 36.771
When I start Tails from USB drive "old" with network unplugged 1:40.082
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 7.024
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.088
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:20.913
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 34.867
And I take note of which tps features are available 1.610
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 8.239
After features/support/hooks.rb:326 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.910
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.455
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.579
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.819
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.567
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.921
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.862
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.638
And I log in to a new session 17.921
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.657
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.766
Then the running Tails is installed on USB drive "to_upgrade" 19.059
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 7.149
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.967
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.386
Then all tps features from the old Tails version are active 1.903
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.261
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.423
After features/support/hooks.rb:326 1.133
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:44.928
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.051
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.527
When the network is plugged 0.071
And Tor is ready 25.222
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.715
Given I shutdown Tails and wait for the computer to power off 13.105
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.447
Then Tails is running version 6.2~testoverlayfs 0.037
And all tps features are active 2.395
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.284
When the network is plugged 0.079
And Tor is ready 21.028
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.625
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 2:6.203
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.394
When the network is plugged 0.077
And Tor is ready 18.156
Then the Upgrader considers the system as up-to-date 0.334
# 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.848
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.125
After features/support/hooks.rb:326 0.860
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
43.215
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.879
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 1.046
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 25.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.741
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.000