Project Number Date
test_Tails_ISO_stable 5023 13 Aug 2024, 08: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:29.300 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:7.102
Before features/support/hooks.rb:269 0.007
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.319
When I start Tails from USB drive "old" with network unplugged 1:32.185
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.098
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.383
After features/support/hooks.rb:326 11.012
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.669
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:21.848
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.349
And I take note of which tps features are available 2.176
Then a Tails persistence partition exists on USB drive "old" 0.947
And I shutdown Tails and wait for the computer to power off 8.788
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.196
Before features/support/hooks.rb:269 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.176
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.279
When I write some files expected to persist 2.090
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.578
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.825
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.420
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.979
And I log in to a new session 25.791
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.497
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.701
Then the running Tails is installed on USB drive "to_upgrade" 17.363
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.540
Before features/support/hooks.rb:269 0.006
Given a computer 0.287
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.762
Then all tps features from the old Tails version are active 1.874
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.465
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:52.451
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.780
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.065
And Tor is ready 24.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.839
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.080
Given I shutdown Tails and wait for the computer to power off 1:26.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.372
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.579
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.313
When the network is plugged 0.102
And Tor is ready 19.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.430
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.919
Given I shutdown Tails and wait for the computer to power off 6.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.253
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.539
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.395
When the network is plugged 0.070
And Tor is ready 18.363
Then the Upgrader considers the system as up-to-date 0.310
# 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 14.352
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
36.920
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.819
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.846
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000