Project Number Date
test_Tails_ISO_stable 4765 03 Apr 2024, 17:57

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:39.910 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:44.848
Before features/support/hooks.rb:245 0.007
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 19.607
When I start Tails from USB drive "old" with network unplugged 1:19.725
Then the boot device has safe access rights 3.141
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:291 3.845
After features/support/hooks.rb:75 0.012
Tags: @product
2:13.132
Before features/support/hooks.rb:245 0.007
Given a computer 1.074
And I start Tails from USB drive "old" with network unplugged and I login 1:22.623
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 37.585
And I take note of which tps features are available 1.612
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.990
After features/support/hooks.rb:291 0.213
After features/support/hooks.rb:75 0.012
Tags: @product
2:53.362
Before features/support/hooks.rb:245 0.006
Given a computer 0.385
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.433
Then Tails is running from USB drive "old" 0.598
And all tps features are active 2.909
When I write some files expected to persist 1.915
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.789
And I take note of which tps features are available 0.936
And I shutdown Tails and wait for the computer to power off 4.390
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.377
After features/support/hooks.rb:291 0.118
After features/support/hooks.rb:75 0.014
Tags: @product
2:22.390
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 13.968
And I log in to a new session 16.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.379
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.119
Then the running Tails is installed on USB drive "to_upgrade" 14.029
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:291 6.929
After features/support/hooks.rb:75 0.000
Tags: @product
2:18.414
Before features/support/hooks.rb:245 0.010
Given a computer 0.725
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.104
Then all tps features from the old Tails version are active 1.924
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.229
And the expected persistent files created with the old Tails version are present in the filesystem 1.639
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:291 0.562
After features/support/hooks.rb:75 0.052
Tags: @product @automatic_upgrade
6:11.418
Before features/support/hooks.rb:245 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.898
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.063
And Tor is ready 16.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.835
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.607
Given I shutdown Tails and wait for the computer to power off 7.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.010
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.317
When the network is plugged 0.041
And Tor is ready 18.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.485
Given I shutdown Tails and wait for the computer to power off 6.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.048
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.044
And Tor is ready 19.068
Then the Upgrader considers the system as up-to-date 0.243
# 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.977
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.884
After features/support/hooks.rb:291 0.798
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
56.343
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
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 0.634
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 44.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.653
After features/support/hooks.rb:291 0.717
After features/support/hooks.rb:75 0.000