Project Number Date
test_Tails_ISO_stable 4904 18 Jun 2024, 23:19

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.492 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:13.358
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.750
When I start Tails from USB drive "old" with network unplugged 1:34.209
Then the boot device has safe access rights 3.046
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.511
After features/support/hooks.rb:100 0.013
Tags: @product
2:11.447
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:28.789
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 32.996
And I take note of which tps features are available 1.742
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 6.432
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.432
Before features/support/hooks.rb:269 0.007
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.311
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.248
When I write some files expected to persist 1.857
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.561
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.407
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.189
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.013
Tags: @product
2:29.392
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.556
And I log in to a new session 18.766
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.449
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.200
Then the running Tails is installed on USB drive "to_upgrade" 20.541
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.132
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.525
Before features/support/hooks.rb:269 0.007
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.808
Then all tps features from the old Tails version are active 1.968
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.968
And the expected persistent files created with the old Tails version are present in the filesystem 1.576
And all persistent directories from the old Tails version have safe access rights 2.573
After features/support/hooks.rb:326 0.936
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:30.363
Before features/support/hooks.rb:269 0.028
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.755
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.069
And Tor is ready 22.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.177
Given I shutdown Tails and wait for the computer to power off 9.159
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.010
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.374
When the network is plugged 0.042
And Tor is ready 19.746
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.122
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.242
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.926
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.051
And Tor is ready 16.251
Then the Upgrader considers the system as up-to-date 0.334
# 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.765
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.036
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.972
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.941
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 20.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.665
After features/support/hooks.rb:326 0.963
After features/support/hooks.rb:100 0.000