Project Number Date
test_Tails_ISO_devel 3624 27 Dec 2024, 12:28

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:16.747 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:0.842
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 27.707
When I start Tails from USB drive "old" with network unplugged 1:27.913
Then the boot device has safe access rights 2.930
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.577
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.572
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:30.247
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.978
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 6.635
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.101
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.712
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.885
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.459
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.492
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.087
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.822
And I log in to a new session 21.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.733
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.410
Then the running Tails is installed on USB drive "to_upgrade" 22.873
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.256
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.170
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.953
Then all tps features from the old Tails version are active 1.551
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.346
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.318
After features/support/hooks.rb:326 1.012
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:55.117
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 11.618
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.074
And Tor is ready 19.365
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.836
Given I shutdown Tails and wait for the computer to power off 8.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.193
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.206
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.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.265
When the network is plugged 0.073
And Tor is ready 19.512
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.234
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.489
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.074
And Tor is ready 46.928
Then the Upgrader considers the system as up-to-date 0.301
# 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.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
35.855
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 9.534
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.382
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 17.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.721
After features/support/hooks.rb:326 1.647
After features/support/hooks.rb:100 0.000