Project Number Date
test_Tails_ISO_devel 3490 23 Aug 2024, 12:50

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:15.351 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:55.334
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.667
When I start Tails from USB drive "old" with network unplugged 1:20.047
Then the boot device has safe access rights 3.172
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.769
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.995
Before features/support/hooks.rb:269 0.007
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:22.992
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.467
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.759
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.483
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.902
Then Tails is running from USB drive "old" 0.310
And all tps features are active 2.053
When I write some files expected to persist 1.688
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.395
And I take note of which tps features are available 0.617
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.408
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.072
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.931
And I log in to a new session 18.465
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.417
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.218
Then the running Tails is installed on USB drive "to_upgrade" 21.226
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 3.407
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.187
Before features/support/hooks.rb:269 0.008
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.795
Then all tps features from the old Tails version are active 1.550
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.929
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.116
After features/support/hooks.rb:326 0.596
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:9.606
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 11.228
And no SquashFS delta is installed 0.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
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.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.099
And Tor is ready 21.713
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.382
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.244
Given I shutdown Tails and wait for the computer to power off 8.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.979
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.256
When the network is plugged 0.083
And Tor is ready 23.548
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.577
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.058
Given I shutdown Tails and wait for the computer to power off 56.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.071
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.985
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.064
And Tor is ready 20.219
Then the Upgrader considers the system as up-to-date 0.299
# 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.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.051
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.672
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.372
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.007
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 20.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.421
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.000