Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 6 01 Feb 2025, 05:06

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 18:27.545 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:0.850
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.262
When I start Tails from USB drive "old" with network unplugged 1:26.189
Then the boot device has safe access rights 3.071
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.785
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.370
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:23.395
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 33.194
And I take note of which tps features are available 1.304
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.212
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.272
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.106
Then Tails is running from USB drive "old" 0.594
And all tps features are active 1.975
When I write some files expected to persist 1.721
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.651
And all persistent directories from the old Tails version have safe access rights 2.909
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.262
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.183
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.734
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 9.932
And I log in to a new session 19.957
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.428
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.264
Then the running Tails is installed on USB drive "to_upgrade" 23.379
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 0.989
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.012
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.690
Then all tps features from the old Tails version are active 1.623
And Tails is running from USB drive "to_upgrade" 0.395
And the boot device has safe access rights 3.146
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.521
After features/support/hooks.rb:326 0.944
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:14.011
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 11.288
And no SquashFS delta is installed 0.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.075
And Tor is ready 21.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.112
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.163
Given I shutdown Tails and wait for the computer to power off 10.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.698
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.260
When the network is plugged 0.068
And Tor is ready 19.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.049
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.900
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.017
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.087
And Tor is ready 16.852
Then the Upgrader considers the system as up-to-date 0.303
# 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 14.547
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.859
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.292
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 9.977
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.977
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.090
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 19.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.122
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.000