Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 5 11 Nov 2024, 10: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:29.730 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:12.851
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.216
When I start Tails from USB drive "old" with network unplugged 1:34.815
Then the boot device has safe access rights 3.301
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.257
After features/support/hooks.rb:326 3.831
After features/support/hooks.rb:100 0.012
Tags: @product
2:11.696
Before features/support/hooks.rb:269 0.008
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:27.660
Then Tails is running from USB drive "old" 1.331
And I create a persistent partition 31.564
And I take note of which tps features are available 1.765
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.362
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.340
Before features/support/hooks.rb:269 0.006
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.276
Then Tails is running from USB drive "old" 0.578
And all tps features are active 2.183
When I write some files expected to persist 1.866
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.539
And all persistent directories from the old Tails version have safe access rights 3.186
And I take note of which tps features are available 0.867
And I shutdown Tails and wait for the computer to power off 4.491
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.858
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.687
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 10.984
And I log in to a new session 20.461
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.580
And I plug USB drive "to_upgrade" 2.531
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.636
Then the running Tails is installed on USB drive "to_upgrade" 20.040
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.229
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.023
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.341
Then all tps features from the old Tails version are active 1.687
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.539
And all persistent directories from the old Tails version have safe access rights 2.618
After features/support/hooks.rb:326 1.064
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:45.437
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 13.344
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.070
And Tor is ready 18.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.368
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.147
Given I shutdown Tails and wait for the computer to power off 11.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.715
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.335
When the network is plugged 0.100
And Tor is ready 13.661
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.084
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.985
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.474
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.749
And only the 6.3~testoverlayfs SquashFS delta is installed 0.122
# 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.542
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.085
And Tor is ready 15.298
Then the Upgrader considers the system as up-to-date 10.789
# 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.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:326 1.090
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
35.692
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.688
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.706
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.856
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 15.341
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.949
After features/support/hooks.rb:326 1.460
After features/support/hooks.rb:100 0.000