Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 13 13 Feb 2025, 04:49

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:59.945 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:2.357
Before features/support/hooks.rb:269 0.002
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.476
When I start Tails from USB drive "old" with network unplugged 1:27.710
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.479
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.089
Before features/support/hooks.rb:269 0.002
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:25.519
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 32.813
And I take note of which tps features are available 1.883
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:326 0.258
After features/support/hooks.rb:100 0.006
Tags: @product
2:59.148
Before features/support/hooks.rb:269 0.002
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.903
Then Tails is running from USB drive "old" 0.399
And all tps features are active 2.167
When I write some files expected to persist 1.665
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.400
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.266
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.093
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.005
Tags: @product
2:38.987
Before features/support/hooks.rb:269 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.070
And I log in to a new session 21.070
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.890
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.627
Then the running Tails is installed on USB drive "to_upgrade" 26.491
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 1.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.630
Before features/support/hooks.rb:269 0.002
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.089
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.184
And the expected persistent files created with the old Tails version are present in the filesystem 1.724
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:326 0.653
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:48.052
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.168
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.064
And Tor is ready 48.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.057
Given I shutdown Tails and wait for the computer to power off 10.934
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.764
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.270
When the network is plugged 0.108
And Tor is ready 17.106
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.130
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.046
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.035
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.017
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.066
And Tor is ready 19.009
Then the Upgrader considers the system as up-to-date 0.416
# 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.715
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.722
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
58.679
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.457
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 47.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.593
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.000