Project Number Date
test_Tails_ISO_20950-remove-sshfs 1 13 May 2025, 13:49

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 19:33.708 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:10.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.642
When I start Tails from USB drive "old" with network unplugged 1:34.234
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 7.298
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:30.120
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 33.863
And I take note of which tps features are available 2.587
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.443
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.230
Then Tails is running from USB drive "old" 0.995
And all tps features are active 1.859
When I write some files expected to persist 1.853
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.406
And all persistence configuration files have safe access rights 0.996
And all persistent directories from the old Tails version have safe access rights 3.324
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 6.554
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.165
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.441
And I log in to a new session 19.693
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.029
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.521
Then the running Tails is installed on USB drive "to_upgrade" 23.091
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 2.273
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.393
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.360
Then all tps features from the old Tails version are active 1.562
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.538
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:330 1.416
After features/support/hooks.rb:100 0.009
6:44.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.744
And no SquashFS delta is installed 0.184
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.501
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.095
And Tor is ready 24.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.104
Given I shutdown Tails and wait for the computer to power off 8.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.002
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.259
When the network is plugged 0.059
And Tor is ready 19.925
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.512
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.694
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.316
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.933
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.065
And Tor is ready 20.802
Then the Upgrader considers the system as up-to-date 0.318
# 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.514
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.704
After features/support/hooks.rb:330 0.796
After features/support/hooks.rb:100 0.019
36.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.733
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.689
After features/support/hooks.rb:330 1.003
After features/support/hooks.rb:100 0.000