Project Number Date
test_Tails_ISO_20522-ocr-more 26 04 Jan 2025, 05:15

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.323 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:3.846
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
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" 30.332
When I start Tails from USB drive "old" with network unplugged 1:28.122
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.559
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.542
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:23.096
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 31.407
And I take note of which tps features are available 2.126
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 8.503
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:59.619
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.649
Then Tails is running from USB drive "old" 1.579
And all tps features are active 2.307
When I write some files expected to persist 3.104
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.852
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.420
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.374
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.011
Tags: @product
2:49.356
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 17.277
And I log in to a new session 25.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.743
And I plug USB drive "to_upgrade" 4.033
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.746
Then the running Tails is installed on USB drive "to_upgrade" 21.765
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.089
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.211
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.591
Then all tps features from the old Tails version are active 1.914
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:326 1.433
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:6.505
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 12.838
And no SquashFS delta is installed 0.332
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.398
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.074
And Tor is ready 23.934
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.112
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.157
Given I shutdown Tails and wait for the computer to power off 10.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.504
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.462
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.326
When the network is plugged 0.065
And Tor is ready 46.730
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.203
Given I shutdown Tails and wait for the computer to power off 6.971
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.298
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.619
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.097
And Tor is ready 14.078
Then the Upgrader considers the system as up-to-date 10.873
# 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 16.603
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.241
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.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.131
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 17.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.294
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.000