Project Number Date
test_Tails_ISO_stable 4903 18 Jun 2024, 22:12

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:58.127 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
3:26.288
Before features/support/hooks.rb:269 0.004
Given a computer 2.282
And I create a 7200 MiB disk named "old" 0.634
And I plug USB drive "old" 1.312
And I write an old version of the Tails USB image to disk "old" 1:21.264
When I start Tails from USB drive "old" with network unplugged 1:56.277
Then the boot device has safe access rights 3.403
And Tails is running from USB drive "old" 0.418
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.736
After features/support/hooks.rb:100 0.013
Tags: @product
2:24.761
Before features/support/hooks.rb:269 0.011
Given a computer 0.330
And I start Tails from USB drive "old" with network unplugged and I login 1:39.738
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 32.252
And I take note of which tps features are available 2.168
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 9.032
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.549
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.387
Then Tails is running from USB drive "old" 0.392
And all tps features are active 3.260
When I write some files expected to persist 1.882
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.095
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.489
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.236
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 17.276
And I log in to a new session 18.533
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.472
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.441
Then the running Tails is installed on USB drive "to_upgrade" 19.676
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.531
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.128
Before features/support/hooks.rb:269 0.005
Given a computer 0.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.159
Then all tps features from the old Tails version are active 1.864
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.409
And the expected persistent files created with the old Tails version are present in the filesystem 1.756
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.875
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 11.036
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.054
And Tor is ready 20.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.904
Given I shutdown Tails and wait for the computer to power off 9.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.833
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.321
When the network is plugged 0.044
And Tor is ready 20.393
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.659
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.873
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.494
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.068
And Tor is ready 20.360
Then the Upgrader considers the system as up-to-date 0.361
# 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.923
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.036
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.287
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 10.380
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.880
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 20.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.265
After features/support/hooks.rb:326 0.809
After features/support/hooks.rb:100 0.000