Project Number Date
test_Tails_ISO_devel 3481 15 Aug 2024, 12:52

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:32.026 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:11.784
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 29.365
When I start Tails from USB drive "old" with network unplugged 1:36.802
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.245
After features/support/hooks.rb:326 3.618
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.732
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:45.860
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 35.215
And I take note of which tps features are available 1.861
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.369
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.689
Before features/support/hooks.rb:269 0.005
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.674
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.280
When I write some files expected to persist 2.231
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.450
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.152
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.107
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.547
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.164
And I log in to a new session 18.642
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.598
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.691
Then the running Tails is installed on USB drive "to_upgrade" 20.502
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 4.600
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.647
Before features/support/hooks.rb:269 0.007
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.808
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.489
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:22.337
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 18.960
And no SquashFS delta is installed 0.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.564
When the network is plugged 0.094
And Tor is ready 19.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.074
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.215
Given I shutdown Tails and wait for the computer to power off 11.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.300
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.454
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.401
When the network is plugged 0.103
And Tor is ready 45.122
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.695
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.611
Given I shutdown Tails and wait for the computer to power off 4.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.956
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.137
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.090
And Tor is ready 18.062
Then the Upgrader considers the system as up-to-date 0.345
# 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.337
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.954
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.287
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 10.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the signing key used by the Upgrader is outdated 1.032
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 18.997
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.720
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.000