Project Number Date
test_Tails_ISO_stable 4813 27 Apr 2024, 12:29

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:22.539 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.397
Before features/support/hooks.rb:259 0.010
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 30.237
When I start Tails from USB drive "old" with network unplugged 1:31.722
Then the boot device has safe access rights 3.056
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:305 3.660
After features/support/hooks.rb:89 0.009
Tags: @product
2:14.971
Before features/support/hooks.rb:259 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:27.258
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 36.310
And I take note of which tps features are available 1.599
Then a Tails persistence partition exists on USB drive "old" 0.763
And I shutdown Tails and wait for the computer to power off 8.470
After features/support/hooks.rb:305 0.130
After features/support/hooks.rb:89 0.009
Tags: @product
2:59.758
Before features/support/hooks.rb:259 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.168
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.288
When I write some files expected to persist 2.085
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.447
And I take note of which tps features are available 0.793
And I shutdown Tails and wait for the computer to power off 4.519
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.225
After features/support/hooks.rb:305 0.114
After features/support/hooks.rb:89 0.009
Tags: @product
2:30.640
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.389
And I log in to a new session 19.835
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.187
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.610
Then the running Tails is installed on USB drive "to_upgrade" 18.697
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:305 5.094
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.472
Before features/support/hooks.rb:259 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.841
Then all tps features from the old Tails version are active 1.788
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 3.309
And the expected persistent files created with the old Tails version are present in the filesystem 1.509
And all persistent directories from the old Tails version have safe access rights 2.438
After features/support/hooks.rb:305 1.081
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
6:36.103
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.565
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.050
And Tor is ready 21.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.162
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.356
Given I shutdown Tails and wait for the computer to power off 9.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.846
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
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.362
# 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.299
When the network is plugged 0.037
And Tor is ready 18.531
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.960
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.780
Given I shutdown Tails and wait for the computer to power off 4.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.051
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.082
And Tor is ready 18.064
Then the Upgrader considers the system as up-to-date 0.307
# 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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.928
After features/support/hooks.rb:305 0.740
After features/support/hooks.rb:89 0.023
Tags: @product @automatic_upgrade
37.194
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.545
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 16.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.699
After features/support/hooks.rb:305 0.791
After features/support/hooks.rb:89 0.000