Project Number Date
test_Tails_ISO_stable 4726 18 Mar 2024, 18: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 17:20.569 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:53.026
Before features/support/hooks.rb:245 0.005
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 37.439
When I start Tails from USB drive "old" with network unplugged 1:10.244
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:291 6.660
After features/support/hooks.rb:75 0.010
Tags: @product
1:58.746
Before features/support/hooks.rb:245 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:17.806
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 30.596
And I take note of which tps features are available 1.980
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 7.035
After features/support/hooks.rb:291 0.211
After features/support/hooks.rb:75 0.013
Tags: @product
2:26.892
Before features/support/hooks.rb:245 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.757
Then Tails is running from USB drive "old" 0.324
And all tps features are active 2.003
When I write some files expected to persist 1.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.388
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.021
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.394
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.010
Tags: @product
2:18.599
Before features/support/hooks.rb:245 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 10.377
And I log in to a new session 15.901
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.469
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.614
Then the running Tails is installed on USB drive "to_upgrade" 13.409
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:291 6.501
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.265
Before features/support/hooks.rb:245 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.950
Then all tps features from the old Tails version are active 1.412
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 2.877
And the expected persistent files created with the old Tails version are present in the filesystem 1.292
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:291 0.909
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:7.889
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.368
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.040
And Tor is ready 18.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.348
Given I shutdown Tails and wait for the computer to power off 6.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.462
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.022
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.258
When the network is plugged 0.043
And Tor is ready 16.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.439
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.997
Given I shutdown Tails and wait for the computer to power off 4.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.386
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.922
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.439
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.074
And Tor is ready 13.503
Then the Upgrader considers the system as up-to-date 10.643
# 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 13.148
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.902
After features/support/hooks.rb:291 0.761
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
33.148
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.602
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 15.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.732
After features/support/hooks.rb:291 0.742
After features/support/hooks.rb:75 0.000