Project Number Date
test_Tails_ISO_devel 3442 30 Jun 2024, 12:48

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 20:7.273 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:58.739
Before features/support/hooks.rb:269 0.007
Given a computer 0.306
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 52.402
When I start Tails from USB drive "old" with network unplugged 2:0.856
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.032
Tags: @product
2:16.137
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:29.529
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 35.312
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 8.454
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.729
Before features/support/hooks.rb:269 0.005
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.169
Then Tails is running from USB drive "old" 0.318
And all tps features are active 2.081
When I write some files expected to persist 2.122
# 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.437
And all persistent directories from the old Tails version have safe access rights 2.572
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 4.456
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.433
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.435
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.103
And I log in to a new session 18.050
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.343
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.408
Then the running Tails is installed on USB drive "to_upgrade" 18.686
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 1.709
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.283
Before features/support/hooks.rb:269 0.006
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.843
Then all tps features from the old Tails version are active 1.611
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.332
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.377
After features/support/hooks.rb:326 1.066
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.138
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 11.376
And no SquashFS delta is installed 0.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.048
And Tor is ready 47.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.626
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.818
Given I shutdown Tails and wait for the computer to power off 9.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.537
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
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.306
# 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.345
When the network is plugged 0.047
And Tor is ready 19.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.307
Given I shutdown Tails and wait for the computer to power off 6.501
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.647
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.552
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.043
And Tor is ready 20.145
Then the Upgrader considers the system as up-to-date 0.326
# 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.409
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.894
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
34.809
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 10.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.560
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 16.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.481
After features/support/hooks.rb:326 0.895
After features/support/hooks.rb:100 0.000