Project Number Date
test_Tails_ISO_stable 5139 03 Oct 2024, 20:33

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 21:18.448 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:50.665
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:12.984
When I start Tails from USB drive "old" with network unplugged 1:31.998
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.581
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.862
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:24.750
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.420
And I take note of which tps features are available 1.767
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 6.444
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.107
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.119
Then Tails is running from USB drive "old" 0.504
And all tps features are active 3.600
When I write some files expected to persist 2.352
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 0.647
And I shutdown Tails and wait for the computer to power off 4.825
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.644
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.881
Before features/support/hooks.rb:269 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 33.552
And I log in to a new session 19.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.696
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.292
Then the running Tails is installed on USB drive "to_upgrade" 19.941
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 7.532
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.579
Before features/support/hooks.rb:269 0.006
Given a computer 0.265
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.614
Then all tps features from the old Tails version are active 1.931
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.433
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:12.385
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 41.529
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.861
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
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.494
When the network is plugged 0.429
And Tor is ready 20.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.200
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.616
Given I shutdown Tails and wait for the computer to power off 13.236
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.011
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.515
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.309
When the network is plugged 0.082
And Tor is ready 21.406
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.615
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.372
Given I shutdown Tails and wait for the computer to power off 6.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.081
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.795
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.360
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.365
When the network is plugged 0.087
And Tor is ready 16.040
Then the Upgrader considers the system as up-to-date 0.312
# 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.527
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.071
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
44.966
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.612
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 1.056
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 20.919
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.157
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.000