Project Number Date
test_Tails_ISO_devel 3609 11 Dec 2024, 13:08

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:15.000 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:25.259
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 33.449
When I start Tails from USB drive "old" with network unplugged 1:45.595
Then the boot device has safe access rights 3.620
And Tails is running from USB drive "old" 0.459
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 15.985
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.192
Before features/support/hooks.rb:269 0.005
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:28.769
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.920
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.571
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.012
Tags: @product
3:7.398
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.490
Then Tails is running from USB drive "old" 0.863
And all tps features are active 2.324
When I write some files expected to persist 2.471
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 2.671
And I take note of which tps features are available 0.553
And I shutdown Tails and wait for the computer to power off 4.181
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.865
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.013
Tags: @product
2:52.876
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 12.570
And I log in to a new session 21.091
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.746
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.049
Then the running Tails is installed on USB drive "to_upgrade" 30.358
And I unplug USB drive "to_upgrade" 0.269
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:326 2.258
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.538
Before features/support/hooks.rb:269 0.010
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.575
Then all tps features from the old Tails version are active 1.802
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.251
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.731
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:21.234
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.268
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.093
And Tor is ready 24.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.433
Given I shutdown Tails and wait for the computer to power off 13.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.702
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.347
When the network is plugged 0.093
And Tor is ready 20.525
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.369
Given I shutdown Tails and wait for the computer to power off 4.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.893
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.450
And the file system changes introduced in version 6.3~testoverlayfs are present 0.761
And only the 6.3~testoverlayfs SquashFS delta is installed 0.123
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.086
And Tor is ready 18.077
Then the Upgrader considers the system as up-to-date 10.925
# 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 16.371
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
42.500
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 13.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 1.057
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.102
After features/support/hooks.rb:326 1.230
After features/support/hooks.rb:100 0.000