Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 31 31 Aug 2024, 07:27

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:24.277 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:18.034
Before features/support/hooks.rb:269 0.006
Given a computer 0.270
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.971
When I start Tails from USB drive "old" with network unplugged 1:40.168
Then the boot device has safe access rights 3.441
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.407
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:27.022
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 31.388
And I take note of which tps features are available 1.949
Then a Tails persistence partition exists on USB drive "old" 0.899
And I shutdown Tails and wait for the computer to power off 8.587
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.195
Before features/support/hooks.rb:269 0.008
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.625
Then Tails is running from USB drive "old" 0.455
And all tps features are active 2.590
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.674
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.102
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.014
Tags: @product
2:45.876
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.574
And I log in to a new session 22.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.007
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.332
Then the running Tails is installed on USB drive "to_upgrade" 25.080
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 2.697
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.476
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.000
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.883
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.696
After features/support/hooks.rb:326 0.925
After features/support/hooks.rb:100 0.013
7:8.613
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 13.530
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.085
And Tor is ready 21.304
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.158
Given I shutdown Tails and wait for the computer to power off 9.106
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.796
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.296
When the network is plugged 0.107
And Tor is ready 18.227
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.101
Given I shutdown Tails and wait for the computer to power off 4.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.856
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.423
And the file system changes introduced in version 6.3~testoverlayfs are present 0.722
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.361
And Tor is ready 17.417
Then the Upgrader considers the system as up-to-date 10.900
# 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.621
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.060
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.018
34.673
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 9.985
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.871
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 16.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.541
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.000