Project Number Date
test_Tails_ISO_devel 3620 23 Dec 2024, 12:32

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:30.814 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:13.961
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.744
When I start Tails from USB drive "old" with network unplugged 1:38.881
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.719
After features/support/hooks.rb:100 0.011
Tags: @product
2:9.477
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:26.036
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.488
And I take note of which tps features are available 1.392
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.234
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.469
Before features/support/hooks.rb:269 0.007
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.058
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.074
When I write some files expected to persist 1.876
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.801
And I take note of which tps features are available 0.570
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.416
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.029
Tags: @product
2:32.213
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.529
And I log in to a new session 19.597
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.604
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.360
Then the running Tails is installed on USB drive "to_upgrade" 22.305
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.574
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.670
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.439
Then all tps features from the old Tails version are active 1.912
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.126
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.350
After features/support/hooks.rb:326 1.227
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:32.051
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.333
And no SquashFS delta is installed 0.680
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.640
When the network is plugged 0.072
And Tor is ready 26.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.711
Given I shutdown Tails and wait for the computer to power off 11.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.331
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.292
When the network is plugged 0.106
And Tor is ready 20.773
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.007
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.062
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.516
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.238
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.077
And Tor is ready 17.066
Then the Upgrader considers the system as up-to-date 0.308
# 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 14.871
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.093
After features/support/hooks.rb:326 0.853
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
55.970
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 25.895
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.599
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 1.081
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 21.770
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.424
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.000