Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 14 21 Nov 2024, 10:37

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 20:37.481 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:24.924
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 34.617
When I start Tails from USB drive "old" with network unplugged 1:44.580
Then the boot device has safe access rights 3.260
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:326 3.818
After features/support/hooks.rb:100 0.015
Tags: @product
2:14.956
Before features/support/hooks.rb:269 0.014
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login 1:30.607
Then Tails is running from USB drive "old" 0.418
And I create a persistent partition 32.266
And I take note of which tps features are available 1.866
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.620
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
3:26.615
Before features/support/hooks.rb:269 0.004
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.776
Then Tails is running from USB drive "old" 0.897
And all tps features are active 6.215
When I write some files expected to persist 1.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.634
And I take note of which tps features are available 1.472
And I shutdown Tails and wait for the computer to power off 6.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.572
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.262
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 18.271
And I log in to a new session 22.535
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.966
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.270
Then the running Tails is installed on USB drive "to_upgrade" 22.306
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 8.125
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.907
Before features/support/hooks.rb:269 0.007
Given a computer 0.291
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.091
Then all tps features from the old Tails version are active 1.696
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.613
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.456
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:41.729
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.728
And no SquashFS delta is installed 0.829
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.528
When the network is plugged 0.073
And Tor is ready 23.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.715
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.449
Given I shutdown Tails and wait for the computer to power off 8.752
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.598
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.345
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.396
# 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.339
When the network is plugged 0.088
And Tor is ready 16.303
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.712
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.488
Given I shutdown Tails and wait for the computer to power off 4.495
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.299
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.194
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.436
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.103
And Tor is ready 16.017
Then the Upgrader considers the system as up-to-date 0.336
# 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.443
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
40.084
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 12.229
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.886
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 20.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.832
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.000