Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 18 25 Nov 2024, 10:26

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:45.381 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:26.538
Before features/support/hooks.rb:269 0.005
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.100
And I write an old version of the Tails USB image to disk "old" 34.677
When I start Tails from USB drive "old" with network unplugged 1:45.942
Then the boot device has safe access rights 3.382
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.622
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.316
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:24.544
Then Tails is running from USB drive "old" 0.540
And I create a persistent partition 37.879
And I take note of which tps features are available 1.778
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 8.482
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.133
Before features/support/hooks.rb:269 0.008
Given a computer 0.332
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.212
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.095
When I write some files expected to persist 1.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.618
And I take note of which tps features are available 0.564
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.945
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.098
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 11.602
And I log in to a new session 21.759
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.795
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.723
Then the running Tails is installed on USB drive "to_upgrade" 25.344
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 7.121
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.394
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.893
Then all tps features from the old Tails version are active 1.832
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.798
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.687
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:35.978
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.854
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.862
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.090
And Tor is ready 19.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.478
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.652
Given I shutdown Tails and wait for the computer to power off 11.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.243
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.363
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.328
When the network is plugged 0.071
And Tor is ready 15.658
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.109
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.356
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.666
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.380
When the network is plugged 0.077
And Tor is ready 14.830
Then the Upgrader considers the system as up-to-date 0.321
# 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 16.321
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.127
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.922
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.592
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.929
But a current signing key is available on our website 0.000
When the network is plugged 0.147
And Tor is ready 15.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.307
After features/support/hooks.rb:326 1.020
After features/support/hooks.rb:100 0.000