Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 23 18 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 19:56.562 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:8.968
Before features/support/hooks.rb:269 0.004
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.966
When I start Tails from USB drive "old" with network unplugged 1:32.447
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.105
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.053
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.549
Before features/support/hooks.rb:269 0.003
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:25.872
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.536
And I take note of which tps features are available 1.434
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.359
After features/support/hooks.rb:326 0.266
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.604
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.502
Then Tails is running from USB drive "old" 0.302
And all tps features are active 1.967
When I write some files expected to persist 1.935
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.857
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.262
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.007
Tags: @product
2:39.859
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.727
And I log in to a new session 19.800
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.546
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.184
Then the running Tails is installed on USB drive "to_upgrade" 28.753
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.193
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.708
Then all tps features from the old Tails version are active 1.700
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.440
And the expected persistent files created with the old Tails version are present in the filesystem 1.462
And all persistent directories from the old Tails version have safe access rights 2.331
After features/support/hooks.rb:326 0.640
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:2.248
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 12.544
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
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.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.070
And Tor is ready 24.016
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.773
Given I shutdown Tails and wait for the computer to power off 10.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.562
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.258
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.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.365
When the network is plugged 0.072
And Tor is ready 45.879
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.442
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.869
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.499
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.082
And Tor is ready 19.497
Then the Upgrader considers the system as up-to-date 0.320
# 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.552
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.854
After features/support/hooks.rb:326 0.906
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.139
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 10.127
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.057
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 19.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.105
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.000