Project Number Date
test_Tails_ISO_devel 3503 04 Sep 2024, 23:13

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:55.194 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:6.605
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.406
When I start Tails from USB drive "old" with network unplugged 1:27.222
Then the boot device has safe access rights 3.612
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.528
Before features/support/hooks.rb:269 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:23.982
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 31.187
And I take note of which tps features are available 1.654
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.281
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.254
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.161
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.050
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.671
After features/support/hooks.rb:326 0.242
After features/support/hooks.rb:100 0.011
Tags: @product
2:45.069
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 13.176
And I log in to a new session 19.683
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.536
And I plug USB drive "to_upgrade" 2.774
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.002
Then the running Tails is installed on USB drive "to_upgrade" 27.040
And I unplug USB drive "to_upgrade" 0.413
And I unplug USB drive "__internal" 0.441
After features/support/hooks.rb:326 3.247
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.661
Before features/support/hooks.rb:269 0.007
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.956
Then all tps features from the old Tails version are active 1.877
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.785
After features/support/hooks.rb:326 0.907
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:1.043
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 44.797
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.448
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.131
And Tor is ready 21.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.501
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.839
Given I shutdown Tails and wait for the computer to power off 11.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.583
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.271
When the network is plugged 0.064
And Tor is ready 18.581
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.602
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.149
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.270
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.073
And Tor is ready 16.581
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 14.015
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.031
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.030
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 9.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.836
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.687
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000