Project Number Date
test_Tails_ISO_stable 5295 27 Nov 2024, 09:02

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:25.608 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:15.235
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 32.734
When I start Tails from USB drive "old" with network unplugged 1:36.999
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.743
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.777
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:27.703
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 35.769
And I take note of which tps features are available 2.111
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.741
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.013
Tags: @product
3:1.105
Before features/support/hooks.rb:269 0.008
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.624
Then Tails is running from USB drive "old" 0.682
And all tps features are active 2.231
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.390
And all persistence configuration files have safe access rights 0.789
And all persistent directories from the old Tails version have safe access rights 3.352
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.636
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.776
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.563
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.646
And I log in to a new session 19.870
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.459
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.240
Then the running Tails is installed on USB drive "to_upgrade" 20.516
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.166
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.747
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.886
Then all tps features from the old Tails version are active 1.649
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.604
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.572
After features/support/hooks.rb:326 1.087
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:32.492
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 12.979
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.068
And Tor is ready 19.572
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.896
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.194
Given I shutdown Tails and wait for the computer to power off 8.824
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.136
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.372
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.302
When the network is plugged 0.121
And Tor is ready 21.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.339
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.522
Given I shutdown Tails and wait for the computer to power off 6.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.008
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.372
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.080
And Tor is ready 15.409
Then the Upgrader considers the system as up-to-date 0.328
# 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.252
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.270
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.686
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.537
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.289
And the signing key used by the Upgrader is outdated 0.755
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 20.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.544
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000