Project Number Date
test_Tails_ISO_devel 3763 02 Apr 2025, 23:09

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 18:47.949 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:17.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.411
When I start Tails from USB drive "old" with network unplugged 1:40.289
Then the boot device has safe access rights 3.135
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.794
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:22.659
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.986
And I take note of which tps features are available 1.614
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 8.443
After features/support/hooks.rb:330 0.251
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.969
Then Tails is running from USB drive "old" 0.851
And all tps features are active 2.063
When I write some files expected to persist 1.834
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 3.128
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.106
After features/support/hooks.rb:330 0.089
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.055
And I log in to a new session 19.107
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.599
Then the running Tails is installed on USB drive "to_upgrade" 21.025
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 0.883
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.218
Then all tps features from the old Tails version are active 1.902
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.343
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.412
After features/support/hooks.rb:330 1.684
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:16.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.264
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
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.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.487
When the network is plugged 0.180
And Tor is ready 19.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.711
Given I shutdown Tails and wait for the computer to power off 8.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.588
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.256
When the network is plugged 0.076
And Tor is ready 16.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.013
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.845
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.026
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.063
And Tor is ready 16.852
Then the Upgrader considers the system as up-to-date 0.321
# 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.388
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.854
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 17.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.549
After features/support/hooks.rb:330 0.882
After features/support/hooks.rb:100 0.000