Project Number Date
test_Tails_ISO_stable 5077 06 Sep 2024, 12:36

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:52.200 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:2.740
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.108
When I start Tails from USB drive "old" with network unplugged 1:28.237
Then the boot device has safe access rights 3.036
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.745
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.653
Before features/support/hooks.rb:269 0.007
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login 1:22.071
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.287
And I take note of which tps features are available 1.593
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.866
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.156
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.134
When I write some files expected to persist 1.736
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.412
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.388
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.783
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.576
And I log in to a new session 20.235
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.586
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.458
Then the running Tails is installed on USB drive "to_upgrade" 23.092
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.675
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.794
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.003
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.432
And the boot device has safe access rights 3.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:33.696
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 15.576
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.639
When the network is plugged 0.093
And Tor is ready 17.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.601
Given I shutdown Tails and wait for the computer to power off 10.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.149
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 2.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.309
When the network is plugged 0.085
And Tor is ready 16.179
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.062
Given I shutdown Tails and wait for the computer to power off 4.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.154
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.126
And Tor is ready 21.613
Then the Upgrader considers the system as up-to-date 0.332
# 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.895
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.157
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.666
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 16.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.927
After features/support/hooks.rb:326 0.908
After features/support/hooks.rb:100 0.000