Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 9 04 Feb 2025, 05:14

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:49.145 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
1:54.098
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.957
When I start Tails from USB drive "old" with network unplugged 1:19.702
Then the boot device has safe access rights 3.084
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 3.509
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.657
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:21.283
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.946
And I take note of which tps features are available 1.553
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.444
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.537
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.067
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.477
When I write some files expected to persist 3.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.407
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.303
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.305
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.027
Tags: @product
2:35.370
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.527
And I log in to a new session 20.729
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.792
Then the running Tails is installed on USB drive "to_upgrade" 24.875
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:326 3.568
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.148
Before features/support/hooks.rb:269 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.058
Then all tps features from the old Tails version are active 3.487
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.507
And the expected persistent files created with the old Tails version are present in the filesystem 1.901
And all persistent directories from the old Tails version have safe access rights 2.624
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:32.073
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.397
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.674
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.074
And Tor is ready 19.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.741
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.975
Given I shutdown Tails and wait for the computer to power off 8.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.936
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.158
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.360
When the network is plugged 0.148
And Tor is ready 18.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.751
Given I shutdown Tails and wait for the computer to power off 6.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.152
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.078
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.494
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.091
And Tor is ready 19.844
Then the Upgrader considers the system as up-to-date 0.301
# 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.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.849
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.260
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 9.814
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 18.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.850
After features/support/hooks.rb:326 0.918
After features/support/hooks.rb:100 0.000