Project Number Date
test_Tails_ISO_stable 5223 26 Oct 2024, 12:28

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:0.076 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:10.244
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.665
When I start Tails from USB drive "old" with network unplugged 1:33.709
Then the boot device has safe access rights 3.497
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 7.380
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.420
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:29.015
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 31.466
And I take note of which tps features are available 1.803
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.670
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.999
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.517
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.244
When I write some files expected to persist 1.698
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.521
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.517
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.747
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.398
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 14.436
And I log in to a new session 20.399
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.798
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.559
Then the running Tails is installed on USB drive "to_upgrade" 18.294
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 6.963
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.870
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.846
Then all tps features from the old Tails version are active 1.895
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.852
And all persistent directories from the old Tails version have safe access rights 2.506
After features/support/hooks.rb:326 0.654
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:58.444
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.847
And no SquashFS delta is installed 0.070
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 file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.065
And Tor is ready 20.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.804
Given I shutdown Tails and wait for the computer to power off 13.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.770
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.439
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.345
When the network is plugged 0.069
And Tor is ready 47.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.653
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.083
Given I shutdown Tails and wait for the computer to power off 4.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.538
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.996
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.499
When the network is plugged 0.066
And Tor is ready 16.302
Then the Upgrader considers the system as up-to-date 10.885
# 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.654
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.104
After features/support/hooks.rb:326 0.851
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
39.698
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.878
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.426
After features/support/hooks.rb:326 1.987
After features/support/hooks.rb:100 0.000