Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 2 05 Mar 2025, 21:44

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:58.264 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
1:57.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 27.950
When I start Tails from USB drive "old" with network unplugged 1:24.315
Then the boot device has safe access rights 3.079
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.537
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:21.936
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 32.529
And I take note of which tps features are available 1.436
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.266
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.803
Then Tails is running from USB drive "old" 0.303
And all tps features are active 2.006
When I write some files expected to persist 1.711
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.211
And I take note of which tps features are available 0.371
And I shutdown Tails and wait for the computer to power off 4.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.833
After features/support/hooks.rb:330 0.096
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.572
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 9.723
And I log in to a new session 17.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.613
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.227
Then the running Tails is installed on USB drive "to_upgrade" 21.062
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.946
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.235
And the expected persistent files created with the old Tails version are present in the filesystem 1.581
And all persistent directories from the old Tails version have safe access rights 2.165
After features/support/hooks.rb:330 1.217
After features/support/hooks.rb:100 0.009
6:50.176
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.376
And no SquashFS delta is installed 0.177
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.062
And Tor is ready 22.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.406
Given I shutdown Tails and wait for the computer to power off 8.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.952
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.248
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.251
When the network is plugged 0.073
And Tor is ready 46.709
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.574
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.928
Given I shutdown Tails and wait for the computer to power off 4.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.862
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.938
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.279
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.062
And Tor is ready 20.285
Then the Upgrader considers the system as up-to-date 0.319
# 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 14.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.018
36.262
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 9.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.717
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.580
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.107
After features/support/hooks.rb:330 0.943
After features/support/hooks.rb:100 0.000