Project Number Date
test_Tails_ISO_stable 5230 29 Oct 2024, 13:00

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:2.883 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:21.823
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.090
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.226
When I start Tails from USB drive "old" with network unplugged 1:44.353
Then the boot device has safe access rights 3.732
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.805
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.886
Before features/support/hooks.rb:269 0.006
Given a computer 0.575
And I start Tails from USB drive "old" with network unplugged and I login 1:30.022
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 35.091
And I take note of which tps features are available 1.630
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 9.275
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
3:15.213
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.680
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.315
When I write some files expected to persist 1.673
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
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.555
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.114
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.041
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 12.248
And I log in to a new session 22.181
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.056
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.199
Then the running Tails is installed on USB drive "to_upgrade" 20.444
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.265
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.628
Before features/support/hooks.rb:269 0.004
Given a computer 0.362
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.788
Then all tps features from the old Tails version are active 1.716
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.590
And the expected persistent files created with the old Tails version are present in the filesystem 1.376
And all persistent directories from the old Tails version have safe access rights 2.433
After features/support/hooks.rb:326 1.014
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:35.036
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 14.018
And no SquashFS delta is installed 0.311
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.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.086
And Tor is ready 22.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.001
Given I shutdown Tails and wait for the computer to power off 9.054
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.096
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.491
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.284
When the network is plugged 0.064
And Tor is ready 19.723
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.164
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.814
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.206
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.217
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.073
And Tor is ready 17.234
Then the Upgrader considers the system as up-to-date 0.330
# 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.004
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.903
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
40.253
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 9.626
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.678
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.924
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.973
After features/support/hooks.rb:326 1.227
After features/support/hooks.rb:100 0.000