Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 13 12 Aug 2024, 07:17

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:3.452 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:21.319
Before features/support/hooks.rb:269 0.008
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.982
When I start Tails from USB drive "old" with network unplugged 1:44.390
Then the boot device has safe access rights 3.339
And Tails is running from USB drive "old" 0.467
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.403
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.608
After features/support/hooks.rb:100 0.014
Tags: @product
2:11.483
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:27.972
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 32.100
And I take note of which tps features are available 1.643
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.631
Before features/support/hooks.rb:269 0.008
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.798
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.010
When I write some files expected to persist 1.679
# 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.426
And all persistent directories from the old Tails version have safe access rights 2.777
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 4.455
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.095
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.947
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 12.488
And I log in to a new session 22.390
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.673
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.839
Then the running Tails is installed on USB drive "to_upgrade" 22.658
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.297
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.113
Before features/support/hooks.rb:269 0.010
Given a computer 0.300
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.217
Then all tps features from the old Tails version are active 1.570
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:14.518
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 13.350
And no SquashFS delta is installed 0.241
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.071
And Tor is ready 18.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.292
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.264
Given I shutdown Tails and wait for the computer to power off 10.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.511
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.995
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.242
When the network is plugged 0.089
And Tor is ready 18.676
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.040
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.488
Given I shutdown Tails and wait for the computer to power off 4.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.715
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.945
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.094
And Tor is ready 19.841
Then the Upgrader considers the system as up-to-date 0.322
# 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.420
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.969
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.437
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 9.945
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
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.890
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 19.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.103
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.000