Project Number Date
test_Tails_ISO_stable 4816 30 Apr 2024, 12:19

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 21:5.727 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:57.593
Before features/support/hooks.rb:259 0.007
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 58.174
When I start Tails from USB drive "old" with network unplugged 1:53.246
Then the boot device has safe access rights 3.640
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.378
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:305 3.854
After features/support/hooks.rb:89 0.013
Tags: @product
2:38.568
Before features/support/hooks.rb:259 0.008
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login 1:39.550
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 46.933
And I take note of which tps features are available 1.864
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.778
After features/support/hooks.rb:305 0.212
After features/support/hooks.rb:89 0.011
Tags: @product
2:55.675
Before features/support/hooks.rb:259 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.624
Then Tails is running from USB drive "old" 0.402
And all tps features are active 1.981
When I write some files expected to persist 1.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
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.824
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.483
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.196
After features/support/hooks.rb:305 0.126
After features/support/hooks.rb:89 0.010
Tags: @product
2:36.946
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.070
And I log in to a new session 16.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.717
And I plug USB drive "to_upgrade" 2.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.505
Then the running Tails is installed on USB drive "to_upgrade" 19.802
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.290
After features/support/hooks.rb:305 3.577
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.145
Before features/support/hooks.rb:259 0.008
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.853
Then all tps features from the old Tails version are active 1.686
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.771
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.807
After features/support/hooks.rb:305 1.033
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
7:1.007
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.975
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.603
When the network is plugged 0.305
And Tor is ready 22.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.912
Given I shutdown Tails and wait for the computer to power off 13.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.046
Then Tails is running version 6.2~testoverlayfs 0.039
And all tps features are active 2.859
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.352
When the network is plugged 0.049
And Tor is ready 20.952
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.971
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.540
Given I shutdown Tails and wait for the computer to power off 5.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.331
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.251
And the file system changes introduced in version 6.3~testoverlayfs are present 0.698
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.054
And Tor is ready 17.384
Then the Upgrader considers the system as up-to-date 0.402
# 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 16.901
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.212
After features/support/hooks.rb:305 0.854
After features/support/hooks.rb:89 0.027
Tags: @product @automatic_upgrade
37.790
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.511
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 17.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.377
After features/support/hooks.rb:305 0.843
After features/support/hooks.rb:89 0.000