Project Number Date
test_Tails_ISO_devel 3411 02 Jun 2024, 13:20

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:39.200 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:57.255
Before features/support/hooks.rb:265 0.008
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.779
When I start Tails from USB drive "old" with network unplugged 1:20.578
Then the boot device has safe access rights 3.437
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:311 3.558
After features/support/hooks.rb:100 0.076
Tags: @product
2:12.086
Before features/support/hooks.rb:265 0.009
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:25.697
Then Tails is running from USB drive "old" 0.391
And I create a persistent partition 34.860
And I take note of which tps features are available 1.671
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:311 0.144
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.901
Before features/support/hooks.rb:265 0.009
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.052
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.150
When I write some files expected to persist 2.097
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.544
And I take note of which tps features are available 0.651
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.732
After features/support/hooks.rb:311 0.133
After features/support/hooks.rb:100 0.013
Tags: @product
2:32.439
Before features/support/hooks.rb:265 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.001
And I log in to a new session 18.637
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 2.579
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.785
Then the running Tails is installed on USB drive "to_upgrade" 18.579
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:311 2.202
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.332
Before features/support/hooks.rb:265 0.009
Given a computer 0.359
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.547
Then all tps features from the old Tails version are active 1.701
And Tails is running from USB drive "to_upgrade" 0.452
And the boot device has safe access rights 3.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:311 0.732
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:53.868
Before features/support/hooks.rb:265 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.717
And no SquashFS delta is installed 0.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
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.417
When the network is plugged 0.048
And Tor is ready 25.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.462
Given I shutdown Tails and wait for the computer to power off 11.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.658
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.268
When the network is plugged 0.072
And Tor is ready 19.438
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.066
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.608
Given I shutdown Tails and wait for the computer to power off 4.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.616
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.321
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.480
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.462
When the network is plugged 0.043
And Tor is ready 18.477
Then the Upgrader considers the system as up-to-date 0.362
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.076
After features/support/hooks.rb:311 0.843
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
38.317
Before features/support/hooks.rb:265 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.210
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 20.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.536
After features/support/hooks.rb:311 0.677
After features/support/hooks.rb:100 0.000