Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 40 09 Sep 2024, 07:14

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:8.037 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:4.404
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.312
When I start Tails from USB drive "old" with network unplugged 1:29.676
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 7.719
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.076
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:23.053
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 33.473
And I take note of which tps features are available 1.494
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 10.573
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.893
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.066
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.005
When I write some files expected to persist 1.680
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.736
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.393
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.810
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 12.380
And I log in to a new session 20.848
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.409
Then the running Tails is installed on USB drive "to_upgrade" 18.760
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 7.258
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.671
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.788
Then all tps features from the old Tails version are active 2.075
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.200
And the expected persistent files created with the old Tails version are present in the filesystem 1.579
And all persistent directories from the old Tails version have safe access rights 2.434
After features/support/hooks.rb:326 1.038
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:22.398
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.353
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.569
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.256
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.116
And Tor is ready 19.046
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.460
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.056
Given I shutdown Tails and wait for the computer to power off 8.802
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.963
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.429
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.277
When the network is plugged 0.067
And Tor is ready 18.864
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.898
Given I shutdown Tails and wait for the computer to power off 1:7.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.270
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.128
And Tor is ready 17.938
Then the Upgrader considers the system as up-to-date 0.364
# 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.234
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:326 0.837
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.783
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 10.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.495
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 1.087
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 19.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.239
After features/support/hooks.rb:326 0.661
After features/support/hooks.rb:100 0.000