Project Number Date
test_Tails_ISO_stable 4970 24 Jul 2024, 12:08

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 18:33.363 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:0.479
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.138
When I start Tails from USB drive "old" with network unplugged 1:25.063
Then the boot device has safe access rights 3.036
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 7.338
After features/support/hooks.rb:100 0.011
Tags: @product
2:1.214
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:19.448
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 30.843
And I take note of which tps features are available 1.374
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.195
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.936
Before features/support/hooks.rb:269 0.006
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.556
Then Tails is running from USB drive "old" 0.406
And all tps features are active 1.915
When I write some files expected to persist 1.640
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.410
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.253
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.155
Before features/support/hooks.rb:269 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 9.900
And I log in to a new session 17.453
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.650
Then the running Tails is installed on USB drive "to_upgrade" 16.959
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.689
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.861
Before features/support/hooks.rb:269 0.007
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.565
Then all tps features from the old Tails version are active 1.732
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:23.872
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 10.796
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.035
And Tor is ready 19.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.257
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.678
Given I shutdown Tails and wait for the computer to power off 8.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.810
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.285
When the network is plugged 0.055
And Tor is ready 19.997
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.185
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.889
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.677
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.076
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.042
And Tor is ready 18.244
Then the Upgrader considers the system as up-to-date 0.335
# 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.530
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.168
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.842
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 9.478
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.700
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 18.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.553
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.000