Project Number Date
test_Tails_ISO_stable 4759 31 Mar 2024, 11:54

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:22.963 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:31.189
Before features/support/hooks.rb:245 0.006
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 19.203
When I start Tails from USB drive "old" with network unplugged 1:6.712
Then the boot device has safe access rights 3.017
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 6.920
After features/support/hooks.rb:75 0.010
Tags: @product
1:56.740
Before features/support/hooks.rb:245 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:12.936
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 33.116
And I take note of which tps features are available 1.202
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.233
After features/support/hooks.rb:291 0.165
After features/support/hooks.rb:75 0.010
Tags: @product
2:38.963
Before features/support/hooks.rb:245 0.006
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.756
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.663
When I write some files expected to persist 1.488
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.363
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.743
After features/support/hooks.rb:291 0.095
After features/support/hooks.rb:75 0.009
Tags: @product
2:15.407
Before features/support/hooks.rb:245 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 9.402
And I log in to a new session 14.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.785
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.619
Then the running Tails is installed on USB drive "to_upgrade" 12.744
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 6.509
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.559
Before features/support/hooks.rb:245 0.007
Given a computer 0.149
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.140
Then all tps features from the old Tails version are active 1.328
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.825
And the expected persistent files created with the old Tails version are present in the filesystem 1.295
And all persistent directories from the old Tails version have safe access rights 2.527
After features/support/hooks.rb:291 0.615
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
6:34.753
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 10.984
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.046
And Tor is ready 16.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.400
Given I shutdown Tails and wait for the computer to power off 1:0.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.381
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.873
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
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.282
# 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.223
When the network is plugged 0.043
And Tor is ready 16.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.944
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.467
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.601
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.641
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.259
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.029
And Tor is ready 17.735
Then the Upgrader considers the system as up-to-date 0.234
# 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.086
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.852
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
30.349
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.819
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.468
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 14.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.220
After features/support/hooks.rb:291 0.925
After features/support/hooks.rb:75 0.000