Project Number Date
test_Tails_ISO_stable 5333 13 Dec 2024, 12:47

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:28.852 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:1.304
Before features/support/hooks.rb:269 0.010
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.402
When I start Tails from USB drive "old" with network unplugged 1:26.446
Then the boot device has safe access rights 3.111
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 7.404
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.779
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:24.674
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 29.817
And I take note of which tps features are available 1.687
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 6.341
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.597
Before features/support/hooks.rb:269 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.102
Then Tails is running from USB drive "old" 1.651
And all tps features are active 1.988
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.495
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.523
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.892
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.013
Tags: @product
2:44.556
Before features/support/hooks.rb:269 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 24.134
And I log in to a new session 19.200
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.725
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.098
Then the running Tails is installed on USB drive "to_upgrade" 21.574
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.415
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.389
Before features/support/hooks.rb:269 0.004
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.231
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:326 0.953
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:53.158
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.108
And no SquashFS delta is installed 0.803
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.071
And Tor is ready 20.713
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.523
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.517
Given I shutdown Tails and wait for the computer to power off 10.746
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.299
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.266
When the network is plugged 0.081
And Tor is ready 19.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.363
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.450
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.242
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.061
And Tor is ready 21.039
Then the Upgrader considers the system as up-to-date 0.302
# 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.630
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.897
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.066
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.812
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.765
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.269
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.821
After features/support/hooks.rb:326 1.664
After features/support/hooks.rb:100 0.000