Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 27 11 Mar 2025, 05:46

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:45.774 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:12.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 33.685
When I start Tails from USB drive "old" with network unplugged 1:33.163
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:31.026
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 33.007
And I take note of which tps features are available 1.487
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 8.486
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.381
Then Tails is running from USB drive "old" 0.367
And all tps features are active 1.900
When I write some files expected to persist 2.034
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.496
And all persistent directories from the old Tails version have safe access rights 2.517
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.277
After features/support/hooks.rb:330 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.759
And I log in to a new session 21.286
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.336
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.514
Then the running Tails is installed on USB drive "to_upgrade" 27.441
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 3.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.594
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.246
Then all tps features from the old Tails version are active 1.717
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.452
And the expected persistent files created with the old Tails version are present in the filesystem 1.944
And all persistent directories from the old Tails version have safe access rights 2.704
After features/support/hooks.rb:330 1.248
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:35.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.773
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.499
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.082
And Tor is ready 24.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.697
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.027
Given I shutdown Tails and wait for the computer to power off 8.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.899
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.340
When the network is plugged 0.057
And Tor is ready 20.490
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.504
Given I shutdown Tails and wait for the computer to power off 4.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.229
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.080
And Tor is ready 19.667
Then the Upgrader considers the system as up-to-date 0.310
# 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.523
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.676
After features/support/hooks.rb:330 0.784
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
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.063
And Tor is ready 18.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.429
After features/support/hooks.rb:330 0.663
After features/support/hooks.rb:100 0.000