Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 64 03 Oct 2024, 07:23

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:2.758 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:10.718
Before features/support/hooks.rb:269 0.006
Given a computer 0.325
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 27.777
When I start Tails from USB drive "old" with network unplugged 1:37.505
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 8.365
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.339
Before features/support/hooks.rb:269 0.007
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:33.324
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 31.334
And I take note of which tps features are available 1.784
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 6.461
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.494
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.412
Then Tails is running from USB drive "old" 1.075
And all tps features are active 2.376
When I write some files expected to persist 2.084
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.845
And all persistent directories from the old Tails version have safe access rights 2.799
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 4.150
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.656
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.055
Tags: @product
2:47.581
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.685
And I log in to a new session 20.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.466
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.345
Then the running Tails is installed on USB drive "to_upgrade" 26.669
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.609
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.787
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.245
Then all tps features from the old Tails version are active 1.902
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.265
And the expected persistent files created with the old Tails version are present in the filesystem 1.422
And all persistent directories from the old Tails version have safe access rights 2.403
After features/support/hooks.rb:326 0.555
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:53.577
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 12.667
And no SquashFS delta is installed 0.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.411
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.070
And Tor is ready 26.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.013
Given I shutdown Tails and wait for the computer to power off 11.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.684
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.327
When the network is plugged 0.067
And Tor is ready 19.601
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.471
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.765
Given I shutdown Tails and wait for the computer to power off 4.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.201
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.074
And Tor is ready 19.851
Then the Upgrader considers the system as up-to-date 0.351
# 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 16.809
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.335
After features/support/hooks.rb:326 0.952
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.258
Before features/support/hooks.rb:269 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.172
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.045
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.905
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 22.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.172
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.000