Project Number Date
test_Tails_ISO_devel 3530 03 Oct 2024, 21:18

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 22:45.117 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:27.535
Before features/support/hooks.rb:269 0.005
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 54.436
When I start Tails from USB drive "old" with network unplugged 1:27.503
Then the boot device has safe access rights 3.116
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:326 3.579
After features/support/hooks.rb:100 0.012
Tags: @product
2:13.080
Before features/support/hooks.rb:269 0.007
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login 1:28.300
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 32.985
And I take note of which tps features are available 1.952
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.699
Before features/support/hooks.rb:269 0.007
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.911
Then Tails is running from USB drive "old" 0.711
And all tps features are active 2.634
When I write some files expected to persist 2.115
# 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.413
And all persistent directories from the old Tails version have safe access rights 2.456
And I take note of which tps features are available 0.603
And I shutdown Tails and wait for the computer to power off 4.205
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.158
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
3:17.619
Before features/support/hooks.rb:269 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 45.561
And I log in to a new session 20.584
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.937
And I plug USB drive "to_upgrade" 2.484
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.922
Then the running Tails is installed on USB drive "to_upgrade" 23.417
And I unplug USB drive "to_upgrade" 0.283
And I unplug USB drive "__internal" 0.428
After features/support/hooks.rb:326 7.202
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.053
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.964
Then all tps features from the old Tails version are active 1.959
And Tails is running from USB drive "to_upgrade" 0.446
And the boot device has safe access rights 3.677
And the expected persistent files created with the old Tails version are present in the filesystem 1.764
And all persistent directories from the old Tails version have safe access rights 3.047
After features/support/hooks.rb:326 1.043
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:8.717
Before features/support/hooks.rb:269 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.977
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.860
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.576
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.067
And Tor is ready 25.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.708
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.225
Given I shutdown Tails and wait for the computer to power off 1:31.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.582
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.432
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.251
When the network is plugged 0.078
And Tor is ready 21.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.002
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.481
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.783
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.065
And Tor is ready 19.230
Then the Upgrader considers the system as up-to-date 10.888
# 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.642
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.047
After features/support/hooks.rb:326 1.019
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:1.411
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 11.533
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.949
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 47.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.576
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000