Project Number Date
test_Tails_ISO_devel 3681 04 Feb 2025, 05:27

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:16.489 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:23.279
Before features/support/hooks.rb:269 0.003
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 32.211
When I start Tails from USB drive "old" with network unplugged 1:45.202
Then the boot device has safe access rights 3.527
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 7.223
After features/support/hooks.rb:100 0.005
Tags: @product
2:11.325
Before features/support/hooks.rb:269 0.002
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:27.812
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.946
And I take note of which tps features are available 1.597
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.527
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.006
Tags: @product
3:5.624
Before features/support/hooks.rb:269 0.003
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.779
Then Tails is running from USB drive "old" 0.547
And all tps features are active 2.264
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 3.533
And I take note of which tps features are available 0.513
And I shutdown Tails and wait for the computer to power off 4.211
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.997
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.005
Tags: @product
2:41.433
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.813
And I log in to a new session 28.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.713
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.049
Then the running Tails is installed on USB drive "to_upgrade" 19.885
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 3.104
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.788
Before features/support/hooks.rb:269 0.003
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.100
Then all tps features from the old Tails version are active 3.031
And Tails is running from USB drive "to_upgrade" 0.435
And the boot device has safe access rights 3.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:326 1.260
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:53.130
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 14.452
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
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.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.081
And Tor is ready 25.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.888
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.424
Given I shutdown Tails and wait for the computer to power off 8.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.223
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.435
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.532
# 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.289
When the network is plugged 0.059
And Tor is ready 19.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.708
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.338
Given I shutdown Tails and wait for the computer to power off 4.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.892
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.457
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.077
And Tor is ready 18.394
Then the Upgrader considers the system as up-to-date 0.322
# 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 16.024
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.941
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
37.907
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
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 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.486
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.528
After features/support/hooks.rb:326 0.942
After features/support/hooks.rb:100 0.000