Project Number Date
test_Tails_ISO_sysadmin-17987-torbrowser-archive 5 21 Oct 2024, 05:40

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:32.784 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.843
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 29.627
When I start Tails from USB drive "old" with network unplugged 1:37.537
Then the boot device has safe access rights 3.282
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.584
After features/support/hooks.rb:100 0.047
Tags: @product
2:2.844
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:19.903
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 31.604
And I take note of which tps features are available 1.504
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.519
Before features/support/hooks.rb:269 0.004
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.368
Then Tails is running from USB drive "old" 0.979
And all tps features are active 2.248
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 3.039
And I take note of which tps features are available 0.560
And I shutdown Tails and wait for the computer to power off 4.195
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.453
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.016
Tags: @product
2:29.674
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.707
And I log in to a new session 18.099
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.567
Then the running Tails is installed on USB drive "to_upgrade" 19.668
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 2.107
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.465
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.035
Then all tps features from the old Tails version are active 1.676
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.159
And the expected persistent files created with the old Tails version are present in the filesystem 1.384
And all persistent directories from the old Tails version have safe access rights 2.703
After features/support/hooks.rb:326 0.943
After features/support/hooks.rb:100 0.007
7:14.222
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 11.102
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.088
And Tor is ready 18.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.377
Given I shutdown Tails and wait for the computer to power off 10.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.393
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.114
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.273
When the network is plugged 0.104
And Tor is ready 19.292
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.177
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.276
Given I shutdown Tails and wait for the computer to power off 59.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.652
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.080
And Tor is ready 17.195
Then the Upgrader considers the system as up-to-date 0.359
# 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.554
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.045
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.026
35.214
Before features/support/hooks.rb:269 0.041
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.571
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.799
But a current signing key is available on our website 0.000
When the network is plugged 0.139
And Tor is ready 15.676
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.590
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.000