Project Number Date
test_Tails_ISO_20522-ocr-more 40 25 Jan 2025, 05:11

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:35.502 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:11.554
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.137
When I start Tails from USB drive "old" with network unplugged 1:34.254
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 6.989
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.922
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:20.991
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 32.630
And I take note of which tps features are available 1.719
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 6.230
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.901
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.743
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.297
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.366
And I take note of which tps features are available 0.449
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" 23.960
After features/support/hooks.rb:326 0.093
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.901
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 9.705
And I log in to a new session 19.091
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.609
And I plug USB drive "to_upgrade" 2.351
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.256
Then the running Tails is installed on USB drive "to_upgrade" 20.496
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.362
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.416
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.982
Then all tps features from the old Tails version are active 1.649
And Tails is running from USB drive "to_upgrade" 0.464
And the boot device has safe access rights 3.264
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.426
After features/support/hooks.rb:326 1.197
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:17.688
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.320
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.524
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.078
And Tor is ready 20.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.264
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.638
Given I shutdown Tails and wait for the computer to power off 10.853
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.390
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.130
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.332
When the network is plugged 0.088
And Tor is ready 19.714
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.476
Given I shutdown Tails and wait for the computer to power off 4.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.208
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.971
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.095
And Tor is ready 18.800
Then the Upgrader considers the system as up-to-date 0.313
# 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.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.878
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.073
Tags: @product @automatic_upgrade
35.116
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.624
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.234
After features/support/hooks.rb:326 0.607
After features/support/hooks.rb:100 0.000