Project Number Date
test_Tails_ISO_stable 5323 09 Dec 2024, 22: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:11.250 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:12.388
Before features/support/hooks.rb:269 0.003
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.846
When I start Tails from USB drive "old" with network unplugged 1:36.649
Then the boot device has safe access rights 3.216
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.491
After features/support/hooks.rb:326 3.630
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.478
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:28.851
Then Tails is running from USB drive "old" 0.485
And I create a persistent partition 32.180
And I take note of which tps features are available 1.879
Then a Tails persistence partition exists on USB drive "old" 0.931
And I shutdown Tails and wait for the computer to power off 8.945
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.859
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.445
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.275
When I write some files expected to persist 1.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.608
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 5.856
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.215
After features/support/hooks.rb:326 0.255
After features/support/hooks.rb:100 0.012
Tags: @product
2:44.773
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 12.523
And I log in to a new session 22.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.787
And I plug USB drive "to_upgrade" 2.565
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.364
Then the running Tails is installed on USB drive "to_upgrade" 28.509
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.358
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.769
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.904
And the expected persistent files created with the old Tails version are present in the filesystem 1.637
And all persistent directories from the old Tails version have safe access rights 2.729
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:51.999
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.016
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.087
And Tor is ready 23.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.764
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.722
Given I shutdown Tails and wait for the computer to power off 10.732
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.480
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.781
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.460
When the network is plugged 0.086
And Tor is ready 20.714
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.325
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.614
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.794
And the file system changes introduced in version 6.3~testoverlayfs are present 0.613
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.068
And Tor is ready 20.903
Then the Upgrader considers the system as up-to-date 0.429
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.384
After features/support/hooks.rb:326 0.788
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
40.392
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.693
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 1.173
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 20.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.941
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.000