Project Number Date
test_Tails_ISO_devel 3688 12 Feb 2025, 21:42

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:41.738 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.626
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 33.613
When I start Tails from USB drive "old" with network unplugged 1:42.159
Then the boot device has safe access rights 3.405
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.014
Tags: @product
2:11.889
Before features/support/hooks.rb:269 0.010
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login 1:27.366
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 32.597
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.811
After features/support/hooks.rb:326 0.315
After features/support/hooks.rb:100 0.011
Tags: @product
3:9.641
Before features/support/hooks.rb:269 0.007
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.331
Then Tails is running from USB drive "old" 0.489
And all tps features are active 2.179
When I write some files expected to persist 2.090
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.486
And all persistent directories from the old Tails version have safe access rights 2.807
And I take note of which tps features are available 0.597
And I shutdown Tails and wait for the computer to power off 4.050
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.064
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.015
Tags: @product
2:41.170
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.008
And I log in to a new session 22.200
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.860
And I plug USB drive "to_upgrade" 2.533
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.776
Then the running Tails is installed on USB drive "to_upgrade" 22.323
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 2.246
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.279
Before features/support/hooks.rb:269 0.006
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.364
Then all tps features from the old Tails version are active 1.910
And Tails is running from USB drive "to_upgrade" 0.523
And the boot device has safe access rights 3.998
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 2.662
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.306
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 12.995
And no SquashFS delta is installed 0.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.115
And Tor is ready 22.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.024
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.711
Given I shutdown Tails and wait for the computer to power off 11.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.250
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.500
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.439
When the network is plugged 0.091
And Tor is ready 20.708
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.028
Given I shutdown Tails and wait for the computer to power off 6.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.400
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.469
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.084
And Tor is ready 18.529
Then the Upgrader considers the system as up-to-date 0.340
# 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.297
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.057
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
1:2.824
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 12.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
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.092
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 49.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.000