Project Number Date
test_Tails_ISO_stable 5052 28 Aug 2024, 08:53

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:52.706 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:25.036
Before features/support/hooks.rb:269 0.010
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.466
When I start Tails from USB drive "old" with network unplugged 1:46.159
Then the boot device has safe access rights 3.347
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.784
And I unplug USB drive "old" 1.347
After features/support/hooks.rb:326 3.968
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.223
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:27.899
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 36.607
And I take note of which tps features are available 1.803
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.935
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.207
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.302
When I write some files expected to persist 1.914
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.696
And I take note of which tps features are available 0.550
And I shutdown Tails and wait for the computer to power off 4.330
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.682
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.776
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 22.783
And I log in to a new session 20.509
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.753
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.536
Then the running Tails is installed on USB drive "to_upgrade" 21.276
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.199
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.327
Before features/support/hooks.rb:269 0.006
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.416
Then all tps features from the old Tails version are active 1.776
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.558
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:326 1.090
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:10.136
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.516
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.086
And Tor is ready 20.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.091
Given I shutdown Tails and wait for the computer to power off 9.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.793
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.272
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.396
# 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.290
When the network is plugged 0.087
And Tor is ready 47.506
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.676
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.139
Given I shutdown Tails and wait for the computer to power off 4.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.992
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.483
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.097
And Tor is ready 17.523
Then the Upgrader considers the system as up-to-date 0.401
# 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.924
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.260
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
46.270
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 18.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.952
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 20.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.334
After features/support/hooks.rb:326 1.164
After features/support/hooks.rb:100 0.000