Project Number Date
test_Tails_ISO_stable 5301 28 Nov 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 23:35.815 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:21.083
Before features/support/hooks.rb:269 0.009
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.216
When I start Tails from USB drive "old" with network unplugged 1:45.081
Then the boot device has safe access rights 3.384
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.785
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.920
Before features/support/hooks.rb:269 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:30.655
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 33.182
And I take note of which tps features are available 1.820
Then a Tails persistence partition exists on USB drive "old" 2.066
And I shutdown Tails and wait for the computer to power off 8.631
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.099
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.328
Then Tails is running from USB drive "old" 1.068
And all tps features are active 2.275
When I write some files expected to persist 4.158
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.299
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 3.583
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.498
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.789
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.556
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 11.248
And I log in to a new session 20.001
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.310
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.613
Then the running Tails is installed on USB drive "to_upgrade" 19.463
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 1.924
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.636
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:33.187
Then all tps features from the old Tails version are active 2.781
And Tails is running from USB drive "to_upgrade" 0.468
And the boot device has safe access rights 3.717
And the expected persistent files created with the old Tails version are present in the filesystem 1.624
And all persistent directories from the old Tails version have safe access rights 2.637
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:31.083
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.942
And no SquashFS delta is installed 0.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.563
When the network is plugged 0.076
And Tor is ready 22.764
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.854
Given I shutdown Tails and wait for the computer to power off 1:31.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.304
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.421
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.342
When the network is plugged 0.086
And Tor is ready 17.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.426
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.619
Given I shutdown Tails and wait for the computer to power off 1:9.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.635
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 4.425
And the file system changes introduced in version 6.3~testoverlayfs are present 0.787
And only the 6.3~testoverlayfs SquashFS delta is installed 0.122
# 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.691
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.750
When the network is plugged 0.124
And Tor is ready 24.584
Then the Upgrader considers the system as up-to-date 0.411
# 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 18.077
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.386
After features/support/hooks.rb:326 0.978
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
48.435
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 13.880
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the signing key used by the Upgrader is outdated 1.171
But a current signing key is available on our website 0.000
When the network is plugged 0.157
And Tor is ready 23.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.309
After features/support/hooks.rb:326 0.793
After features/support/hooks.rb:100 0.000