Project Number Date
test_Tails_ISO_stable 5429 29 Jan 2025, 08:55

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 19:27.640 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:7.557
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.283
When I start Tails from USB drive "old" with network unplugged 1:30.838
Then the boot device has safe access rights 3.088
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:326 3.731
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.365
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:25.986
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 33.160
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.281
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.454
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.698
Then Tails is running from USB drive "old" 0.923
And all tps features are active 2.264
When I write some files expected to persist 1.801
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.968
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 3.046
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 6.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.116
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.290
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 13.716
And I log in to a new session 20.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.656
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.466
Then the running Tails is installed on USB drive "to_upgrade" 20.606
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 3.625
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.758
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.933
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.261
And the expected persistent files created with the old Tails version are present in the filesystem 1.710
And all persistent directories from the old Tails version have safe access rights 2.502
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
6:50.335
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 11.670
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.126
And Tor is ready 19.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.950
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.950
Given I shutdown Tails and wait for the computer to power off 10.749
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.063
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.279
When the network is plugged 0.078
And Tor is ready 47.424
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.285
Given I shutdown Tails and wait for the computer to power off 4.437
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.950
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.524
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.167
And Tor is ready 18.659
Then the Upgrader considers the system as up-to-date 0.289
# 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.851
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.141
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
34.879
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 9.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.532
After features/support/hooks.rb:326 0.954
After features/support/hooks.rb:100 0.000