Project Number Date
test_Tails_ISO_devel 3676 01 Feb 2025, 17:50

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:22.374 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:7.211
Before features/support/hooks.rb:269 0.002
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 30.973
When I start Tails from USB drive "old" with network unplugged 1:30.702
Then the boot device has safe access rights 3.171
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 9.336
After features/support/hooks.rb:100 0.005
Tags: @product
2:11.216
Before features/support/hooks.rb:269 0.002
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:28.061
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 31.689
And I take note of which tps features are available 1.350
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.006
Tags: @product
2:55.770
Before features/support/hooks.rb:269 0.003
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.923
Then Tails is running from USB drive "old" 1.186
And all tps features are active 3.286
When I write some files expected to persist 2.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.483
And all persistent directories from the old Tails version have safe access rights 2.496
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.515
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.005
Tags: @product
2:26.143
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 9.931
And I log in to a new session 18.208
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.605
Then the running Tails is installed on USB drive "to_upgrade" 19.090
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 6.615
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.813
Before features/support/hooks.rb:269 0.003
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.762
Then all tps features from the old Tails version are active 1.607
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.240
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 3.201
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:49.150
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 13.516
And no SquashFS delta is installed 1.263
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.066
And Tor is ready 21.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.086
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.816
Given I shutdown Tails and wait for the computer to power off 10.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.382
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.248
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.271
When the network is plugged 0.085
And Tor is ready 19.163
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.052
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.195
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.371
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.074
And Tor is ready 48.031
Then the Upgrader considers the system as up-to-date 0.309
# 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.168
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.829
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
41.068
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 11.480
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.379
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 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.314
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.000