Project Number Date
test_Tails_ISO_devel 3602 04 Dec 2024, 12:53

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:47.913 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:22.391
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.841
When I start Tails from USB drive "old" with network unplugged 1:45.044
Then the boot device has safe access rights 4.066
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.014
Tags: @product
2:16.667
Before features/support/hooks.rb:269 0.008
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:32.246
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 31.826
And I take note of which tps features are available 1.866
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 9.198
After features/support/hooks.rb:326 0.244
After features/support/hooks.rb:100 0.015
Tags: @product
2:58.731
Before features/support/hooks.rb:269 0.011
Given a computer 0.324
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.715
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.254
When I write some files expected to persist 2.067
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 3.011
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.782
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.877
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.068
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 12.480
And I log in to a new session 21.735
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.944
And I plug USB drive "to_upgrade" 2.866
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.505
Then the running Tails is installed on USB drive "to_upgrade" 23.068
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 7.205
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.259
Before features/support/hooks.rb:269 0.009
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.201
Then all tps features from the old Tails version are active 1.890
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 4.142
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.834
After features/support/hooks.rb:326 2.012
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:19.184
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.255
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.681
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.080
And Tor is ready 26.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.364
Given I shutdown Tails and wait for the computer to power off 11.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.352
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.878
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.424
When the network is plugged 0.101
And Tor is ready 19.980
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.187
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.268
Given I shutdown Tails and wait for the computer to power off 4.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.432
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.081
And Tor is ready 19.063
Then the Upgrader considers the system as up-to-date 0.332
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.483
After features/support/hooks.rb:326 0.764
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
39.610
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.439
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.151
And the signing key used by the Upgrader is outdated 1.029
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 20.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.997
After features/support/hooks.rb:326 0.934
After features/support/hooks.rb:100 0.000