Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 20 15 Feb 2025, 05:26

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:1.495 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:37.941
Before features/support/hooks.rb:269 0.004
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 1:0.500
When I start Tails from USB drive "old" with network unplugged 1:31.521
Then the boot device has safe access rights 3.222
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.485
After features/support/hooks.rb:326 7.051
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.455
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:26.222
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 31.854
And I take note of which tps features are available 1.569
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.404
After features/support/hooks.rb:326 0.314
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.125
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.979
Then Tails is running from USB drive "old" 0.297
And all tps features are active 2.031
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.365
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.205
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.202
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.972
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 10.484
And I log in to a new session 18.463
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.056
And I plug USB drive "to_upgrade" 2.366
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.207
Then the running Tails is installed on USB drive "to_upgrade" 21.921
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:326 6.946
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.121
Then all tps features from the old Tails version are active 2.021
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.720
And the expected persistent files created with the old Tails version are present in the filesystem 1.484
And all persistent directories from the old Tails version have safe access rights 2.516
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.987
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.598
And no SquashFS delta is installed 0.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.162
And Tor is ready 22.858
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.649
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.019
Given I shutdown Tails and wait for the computer to power off 8.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.453
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.246
When the network is plugged 0.080
And Tor is ready 16.328
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.550
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 4.814
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.658
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.484
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.085
And Tor is ready 18.962
Then the Upgrader considers the system as up-to-date 10.857
# 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.617
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.510
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
38.611
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 10.020
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.160
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.113
And Tor is ready 22.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.037
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000