Project Number Date
test_Tails_ISO_stable 5271 16 Nov 2024, 12:52

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:37.229 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:24.805
Before features/support/hooks.rb:269 0.005
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.871
When I start Tails from USB drive "old" with network unplugged 1:45.926
Then the boot device has safe access rights 3.592
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.641
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.262
Before features/support/hooks.rb:269 0.007
Given a computer 1.104
And I start Tails from USB drive "old" with network unplugged and I login 1:31.565
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 33.234
And I take note of which tps features are available 1.925
Then a Tails persistence partition exists on USB drive "old" 0.964
And I shutdown Tails and wait for the computer to power off 9.082
After features/support/hooks.rb:326 0.226
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.191
Before features/support/hooks.rb:269 0.007
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.700
Then Tails is running from USB drive "old" 1.267
And all tps features are active 3.902
When I write some files expected to persist 2.312
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.498
And all persistent directories from the old Tails version have safe access rights 3.201
And I take note of which tps features are available 0.546
And I shutdown Tails and wait for the computer to power off 4.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.724
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.013
Tags: @product
2:38.219
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 11.868
And I log in to a new session 22.620
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.045
Then the running Tails is installed on USB drive "to_upgrade" 22.049
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 1.173
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.827
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.846
Then all tps features from the old Tails version are active 1.777
And Tails is running from USB drive "to_upgrade" 0.441
And the boot device has safe access rights 3.909
And the expected persistent files created with the old Tails version are present in the filesystem 1.740
And all persistent directories from the old Tails version have safe access rights 2.911
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:6.736
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 13.899
And no SquashFS delta is installed 0.542
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.547
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.645
When the network is plugged 0.106
And Tor is ready 22.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.251
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.941
Given I shutdown Tails and wait for the computer to power off 11.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.628
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.519
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.472
# 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.330
When the network is plugged 0.091
And Tor is ready 20.996
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.781
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.597
Given I shutdown Tails and wait for the computer to power off 4.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.428
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.071
And Tor is ready 18.141
Then the Upgrader considers the system as up-to-date 10.832
# 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 15.560
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.186
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.458
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 2.053
But a current signing key is available on our website 0.000
When the network is plugged 0.214
And Tor is ready 20.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.052
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.000