Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 8 03 Feb 2025, 05:03

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:50.445 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:52.769
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.180
When I start Tails from USB drive "old" with network unplugged 1:16.175
Then the boot device has safe access rights 3.111
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.605
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.267
Before features/support/hooks.rb:269 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login 1:28.214
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 30.589
And I take note of which tps features are available 1.604
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.427
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.872
Before features/support/hooks.rb:269 0.026
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.969
Then Tails is running from USB drive "old" 0.868
And all tps features are active 1.951
When I write some files expected to persist 2.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.552
And I shutdown Tails and wait for the computer to power off 4.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.295
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.354
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.488
And I log in to a new session 19.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.576
And I plug USB drive "to_upgrade" 2.353
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.722
Then the running Tails is installed on USB drive "to_upgrade" 21.414
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 6.491
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.346
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.773
Then all tps features from the old Tails version are active 1.945
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.441
And the expected persistent files created with the old Tails version are present in the filesystem 1.332
And all persistent directories from the old Tails version have safe access rights 2.331
After features/support/hooks.rb:326 0.627
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:32.278
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 14.765
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.071
And Tor is ready 22.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.130
Given I shutdown Tails and wait for the computer to power off 8.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.523
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
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.299
# 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.336
When the network is plugged 0.102
And Tor is ready 17.578
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.987
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.222
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.465
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.936
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.100
And Tor is ready 20.807
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 13.991
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.715
After features/support/hooks.rb:326 1.022
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
34.556
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 9.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.973
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 17.369
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.335
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.000