Project Number Date
test_Tails_ISO_stable 4791 17 Apr 2024, 12:21

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 17:32.656 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:47.619
Before features/support/hooks.rb:259 0.017
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 21.525
When I start Tails from USB drive "old" with network unplugged 1:20.216
Then the boot device has safe access rights 3.411
And Tails is running from USB drive "old" 0.433
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:305 6.892
After features/support/hooks.rb:89 0.010
Tags: @product
2:3.517
Before features/support/hooks.rb:259 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:16.845
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 35.164
And I take note of which tps features are available 1.498
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.643
After features/support/hooks.rb:305 0.232
After features/support/hooks.rb:89 0.012
Tags: @product
2:33.667
Before features/support/hooks.rb:259 0.009
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.893
Then Tails is running from USB drive "old" 0.400
And all tps features are active 1.967
When I write some files expected to persist 1.683
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.723
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.158
After features/support/hooks.rb:305 0.139
After features/support/hooks.rb:89 0.009
Tags: @product
2:23.699
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.986
And I log in to a new session 18.483
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.893
Then the running Tails is installed on USB drive "to_upgrade" 15.016
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:305 2.824
After features/support/hooks.rb:89 0.000
Tags: @product
2:1.941
Before features/support/hooks.rb:259 0.008
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.610
Then all tps features from the old Tails version are active 1.609
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.152
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.632
After features/support/hooks.rb:305 0.731
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:8.131
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.080
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.047
And Tor is ready 20.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.154
Given I shutdown Tails and wait for the computer to power off 6.855
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.007
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.273
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.270
# 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.273
When the network is plugged 0.050
And Tor is ready 14.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.048
Given I shutdown Tails and wait for the computer to power off 4.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.422
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.283
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.065
And Tor is ready 17.643
Then the Upgrader considers the system as up-to-date 0.265
# 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 13.255
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.816
After features/support/hooks.rb:305 0.703
After features/support/hooks.rb:89 0.110
Tags: @product @automatic_upgrade
34.079
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.510
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.099
And the signing key used by the Upgrader is outdated 0.684
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 18.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.258
After features/support/hooks.rb:305 0.668
After features/support/hooks.rb:89 0.000