Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 17 14 Feb 2025, 16:09

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 20:13.696 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.164
Before features/support/hooks.rb:269 0.005
Given a computer 0.240
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.533
When I start Tails from USB drive "old" with network unplugged 1:24.039
Then the boot device has safe access rights 3.147
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 6.703
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.381
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:29.989
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 31.380
And I take note of which tps features are available 2.044
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.578
After features/support/hooks.rb:326 0.304
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.674
Before features/support/hooks.rb:269 0.006
Given a computer 0.337
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.554
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.580
When I write some files expected to persist 1.817
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.739
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.494
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.518
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.023
Tags: @product
3:4.724
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 25.251
And I log in to a new session 20.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.614
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.329
Then the running Tails is installed on USB drive "to_upgrade" 31.350
And I unplug USB drive "to_upgrade" 0.263
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 0.977
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.015
Before features/support/hooks.rb:269 0.006
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.899
Then all tps features from the old Tails version are active 1.703
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 4.173
And the expected persistent files created with the old Tails version are present in the filesystem 1.813
And all persistent directories from the old Tails version have safe access rights 2.784
After features/support/hooks.rb:326 1.396
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
6:43.522
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 15.824
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.470
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.724
When the network is plugged 0.083
And Tor is ready 21.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.212
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.721
Given I shutdown Tails and wait for the computer to power off 11.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.022
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.251
When the network is plugged 0.089
And Tor is ready 19.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.836
Given I shutdown Tails and wait for the computer to power off 4.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.893
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.255
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
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.406
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.067
And Tor is ready 20.092
Then the Upgrader considers the system as up-to-date 0.325
# 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.020
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.759
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.213
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.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.076
And Tor is ready 19.272
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.161
After features/support/hooks.rb:326 1.179
After features/support/hooks.rb:100 0.000