Project Number Date
test_Tails_ISO_stable 4867 03 Jun 2024, 13:55

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:44.481 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:12.463
Before features/support/hooks.rb:265 0.005
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.875
When I start Tails from USB drive "old" with network unplugged 1:35.805
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:311 3.822
After features/support/hooks.rb:100 0.030
Tags: @product
2:14.941
Before features/support/hooks.rb:265 0.010
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:26.525
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 36.686
And I take note of which tps features are available 1.728
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 8.491
After features/support/hooks.rb:311 0.194
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.575
Before features/support/hooks.rb:265 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.774
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.042
When I write some files expected to persist 1.582
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.796
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.415
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.301
After features/support/hooks.rb:311 0.168
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.225
Before features/support/hooks.rb:265 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 11.423
And I log in to a new session 18.471
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.052
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.391
Then the running Tails is installed on USB drive "to_upgrade" 22.050
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:311 1.895
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.080
Before features/support/hooks.rb:265 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.087
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.497
And the boot device has safe access rights 3.572
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.370
After features/support/hooks.rb:311 0.668
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:42.399
Before features/support/hooks.rb:265 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.617
And no SquashFS delta is installed 0.241
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.035
And Tor is ready 19.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.691
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.831
Given I shutdown Tails and wait for the computer to power off 11.383
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.681
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.286
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.292
When the network is plugged 0.068
And Tor is ready 16.538
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.776
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.142
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.046
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.095
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.068
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.036
And Tor is ready 18.469
Then the Upgrader considers the system as up-to-date 0.329
# 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 15.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.906
After features/support/hooks.rb:311 0.949
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.795
Before features/support/hooks.rb:265 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 1.019
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 19.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.514
After features/support/hooks.rb:311 0.816
After features/support/hooks.rb:100 0.000