Project Number Date
test_Tails_ISO_devel 3616 19 Dec 2024, 12:57

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 22:12.173 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:43.668
Before features/support/hooks.rb:269 0.006
Given a computer 0.840
And I create a 7200 MiB disk named "old" 0.300
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:2.693
When I start Tails from USB drive "old" with network unplugged 1:34.587
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.806
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.733
Before features/support/hooks.rb:269 0.005
Given a computer 0.819
And I start Tails from USB drive "old" with network unplugged and I login 1:29.573
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.099
And I take note of which tps features are available 1.689
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.418
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.639
Before features/support/hooks.rb:269 0.006
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.441
Then Tails is running from USB drive "old" 1.040
And all tps features are active 3.104
When I write some files expected to persist 2.534
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.478
And I take note of which tps features are available 0.657
And I shutdown Tails and wait for the computer to power off 4.443
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.004
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
3:5.386
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 33.277
And I log in to a new session 20.096
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.913
And I plug USB drive "to_upgrade" 2.687
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.323
Then the running Tails is installed on USB drive "to_upgrade" 24.552
And I unplug USB drive "to_upgrade" 0.294
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 2.429
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.695
Before features/support/hooks.rb:269 0.005
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:34.167
Then all tps features from the old Tails version are active 2.033
And Tails is running from USB drive "to_upgrade" 0.457
And the boot device has safe access rights 3.436
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.726
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:42.557
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 36.446
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.573
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.114
And Tor is ready 22.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.800
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.645
Given I shutdown Tails and wait for the computer to power off 11.098
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.834
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 4.430
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.368
When the network is plugged 0.542
And Tor is ready 19.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.605
Given I shutdown Tails and wait for the computer to power off 4.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.446
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.685
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.490
When the network is plugged 0.090
And Tor is ready 20.630
Then the Upgrader considers the system as up-to-date 0.356
# 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.525
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.330
After features/support/hooks.rb:326 0.887
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.491
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 11.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.552
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.855
But a current signing key is available on our website 0.000
When the network is plugged 0.382
And Tor is ready 21.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.672
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.000