Project Number Date
test_Tails_ISO_stable 4918 01 Jul 2024, 13:45

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:11.359 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:29.025
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.223
When I start Tails from USB drive "old" with network unplugged 1:54.772
Then the boot device has safe access rights 2.830
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:326 3.499
After features/support/hooks.rb:100 0.015
Tags: @product
2:2.867
Before features/support/hooks.rb:269 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:20.887
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 30.816
And I take note of which tps features are available 1.583
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.786
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.620
Then Tails is running from USB drive "old" 0.323
And all tps features are active 2.140
When I write some files expected to persist 2.348
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.300
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.101
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.562
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.814
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 13.907
And I log in to a new session 21.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.562
And I plug USB drive "to_upgrade" 2.340
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.162
Then the running Tails is installed on USB drive "to_upgrade" 16.604
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.686
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.302
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.719
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.150
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.794
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:25.630
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 12.614
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.399
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.050
And Tor is ready 22.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.770
Given I shutdown Tails and wait for the computer to power off 8.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.060
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.276
When the network is plugged 0.084
And Tor is ready 20.763
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.942
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.322
Given I shutdown Tails and wait for the computer to power off 4.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.583
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.059
And Tor is ready 20.226
Then the Upgrader considers the system as up-to-date 0.314
# 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.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.071
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.931
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 10.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 1.206
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 19.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.760
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.000