Project Number Date
test_Tails_ISO_stable 5115 24 Sep 2024, 20:48

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:57.067 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:5.729
Before features/support/hooks.rb:269 0.007
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 33.526
When I start Tails from USB drive "old" with network unplugged 1:26.528
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.569
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.712
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:27.764
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 31.565
And I take note of which tps features are available 1.461
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.593
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.351
Before features/support/hooks.rb:269 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.646
Then Tails is running from USB drive "old" 0.527
And all tps features are active 2.018
When I write some files expected to persist 1.833
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.551
And all persistent directories from the old Tails version have safe access rights 2.733
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.773
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.788
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.626
And I log in to a new session 18.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.769
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.904
Then the running Tails is installed on USB drive "to_upgrade" 18.632
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.257
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.216
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.330
Then all tps features from the old Tails version are active 1.684
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.701
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.442
After features/support/hooks.rb:326 1.017
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:24.553
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.803
And no SquashFS delta is installed 0.074
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.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.064
And Tor is ready 22.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.732
Given I shutdown Tails and wait for the computer to power off 10.967
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.666
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.150
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.243
When the network is plugged 0.072
And Tor is ready 19.806
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.651
Given I shutdown Tails and wait for the computer to power off 4.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.522
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.074
And Tor is ready 20.086
Then the Upgrader considers the system as up-to-date 0.301
# 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.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.194
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.715
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.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 1.048
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 17.152
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.772
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.000