Project Number Date
test_Tails_ISO_devel 3323 16 Mar 2024, 12:48

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 17:33.156 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:40.895
Before features/support/hooks.rb:245 0.008
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 22.564
When I start Tails from USB drive "old" with network unplugged 1:12.910
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 6.870
After features/support/hooks.rb:75 0.010
Tags: @product
2:10.398
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:19.906
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 41.063
And I take note of which tps features are available 2.042
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 6.069
After features/support/hooks.rb:291 0.166
After features/support/hooks.rb:75 0.012
Tags: @product
2:33.253
Before features/support/hooks.rb:245 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.849
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.368
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.024
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.787
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.011
Tags: @product
2:36.327
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.882
And I log in to a new session 20.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.322
Then the running Tails is installed on USB drive "to_upgrade" 13.272
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 0.873
After features/support/hooks.rb:75 0.000
Tags: @product
2:12.157
Before features/support/hooks.rb:245 0.010
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.409
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.052
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.331
After features/support/hooks.rb:291 0.739
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:49.140
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.350
And no SquashFS delta is installed 0.086
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.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.055
And Tor is ready 19.071
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.363
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.151
Given I shutdown Tails and wait for the computer to power off 9.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.685
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.276
When the network is plugged 0.032
And Tor is ready 15.898
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.275
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.865
Given I shutdown Tails and wait for the computer to power off 5.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.071
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.897
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.039
And Tor is ready 17.024
Then the Upgrader considers the system as up-to-date 0.235
# 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 12.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:291 0.732
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
30.984
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.423
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 1.214
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 14.659
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.327
After features/support/hooks.rb:291 1.222
After features/support/hooks.rb:75 0.000