Project Number Date
test_Tails_ISO_stable 4879 09 Jun 2024, 12:36

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 18:37.503 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
1:59.082
Before features/support/hooks.rb:269 0.006
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.044
When I start Tails from USB drive "old" with network unplugged 1:23.685
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:315 3.519
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.844
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:20.875
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 36.051
And I take note of which tps features are available 1.382
Then a Tails persistence partition exists on USB drive "old" 0.773
And I shutdown Tails and wait for the computer to power off 8.214
After features/support/hooks.rb:315 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.549
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.344
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.996
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.542
And I take note of which tps features are available 0.368
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.193
After features/support/hooks.rb:315 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.662
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.736
And I log in to a new session 18.003
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.469
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.988
Then the running Tails is installed on USB drive "to_upgrade" 20.649
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:315 1.820
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.932
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.153
Then all tps features from the old Tails version are active 1.530
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.953
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.245
After features/support/hooks.rb:315 0.815
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
6:30.595
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 10.726
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.057
And Tor is ready 22.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.166
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.486
Given I shutdown Tails and wait for the computer to power off 8.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.957
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.447
# 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.285
When the network is plugged 0.045
And Tor is ready 45.745
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.276
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.929
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.950
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.062
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.046
And Tor is ready 19.477
Then the Upgrader considers the system as up-to-date 0.314
# 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.901
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.948
After features/support/hooks.rb:315 0.891
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.836
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 9.967
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.322
But a current signing key is available on our website 0.000
When the network is plugged 0.413
And Tor is ready 18.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.579
After features/support/hooks.rb:315 0.833
After features/support/hooks.rb:100 0.000