Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 13 20 Nov 2024, 10:18

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:53.967 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.843
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.379
When I start Tails from USB drive "old" with network unplugged 1:36.843
Then the boot device has safe access rights 3.286
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.554
After features/support/hooks.rb:100 0.030
Tags: @product
2:15.557
Before features/support/hooks.rb:269 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:32.992
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 30.994
And I take note of which tps features are available 1.766
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.776
Before features/support/hooks.rb:269 0.004
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.230
Then Tails is running from USB drive "old" 0.454
And all tps features are active 3.644
When I write some files expected to persist 1.891
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.018
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.930
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.553
And I log in to a new session 21.817
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.645
And I plug USB drive "to_upgrade" 2.505
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.454
Then the running Tails is installed on USB drive "to_upgrade" 23.539
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.516
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.162
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.316
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.475
And all persistent directories from the old Tails version have safe access rights 2.991
After features/support/hooks.rb:326 0.927
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:52.545
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 17.911
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.780
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.549
When the network is plugged 0.075
And Tor is ready 18.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.910
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.508
Given I shutdown Tails and wait for the computer to power off 10.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.285
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.647
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.341
When the network is plugged 0.118
And Tor is ready 15.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.552
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.608
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.799
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.486
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.083
And Tor is ready 13.843
Then the Upgrader considers the system as up-to-date 10.895
# 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.320
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:326 1.068
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
37.151
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 1.187
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 17.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.624
After features/support/hooks.rb:326 1.078
After features/support/hooks.rb:100 0.000