Project Number Date
test_Tails_ISO_devel 3667 28 Jan 2025, 18:04

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:23.107 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:22.056
Before features/support/hooks.rb:269 0.002
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.737
When I start Tails from USB drive "old" with network unplugged 1:44.488
Then the boot device has safe access rights 3.455
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 7.203
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.986
Before features/support/hooks.rb:269 0.002
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:30.402
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 33.509
And I take note of which tps features are available 1.886
Then a Tails persistence partition exists on USB drive "old" 1.051
And I shutdown Tails and wait for the computer to power off 8.569
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.006
Tags: @product
2:53.183
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.933
Then Tails is running from USB drive "old" 0.374
And all tps features are active 2.014
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.711
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.076
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.758
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.382
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.048
And I log in to a new session 21.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.005
And I plug USB drive "to_upgrade" 2.544
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.976
Then the running Tails is installed on USB drive "to_upgrade" 27.651
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.372
After features/support/hooks.rb:326 2.701
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.262
Before features/support/hooks.rb:269 0.003
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.528
Then all tps features from the old Tails version are active 2.131
And Tails is running from USB drive "to_upgrade" 0.441
And the boot device has safe access rights 4.025
And the expected persistent files created with the old Tails version are present in the filesystem 1.866
And all persistent directories from the old Tails version have safe access rights 3.050
After features/support/hooks.rb:326 1.123
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:52.364
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 15.479
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
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.486
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.657
When the network is plugged 0.088
And Tor is ready 21.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.975
Given I shutdown Tails and wait for the computer to power off 11.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.030
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.346
When the network is plugged 0.094
And Tor is ready 17.382
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.806
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.165
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:3.250
Then Tails is running version 6.3~testoverlayfs 0.037
And all tps features are active 2.039
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.123
And Tor is ready 20.319
Then the Upgrader considers the system as up-to-date 0.306
# 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.149
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.321
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
39.870
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 11.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.622
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 19.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.756
After features/support/hooks.rb:326 1.426
After features/support/hooks.rb:100 0.000