Project Number Date
test_Tails_ISO_20522-ocr-more 42 27 Jan 2025, 05:18

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:44.972 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:10.706
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.096
And I plug USB drive "old" 1.299
And I write an old version of the Tails USB image to disk "old" 34.126
When I start Tails from USB drive "old" with network unplugged 1:30.976
Then the boot device has safe access rights 3.064
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.504
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.005
Before features/support/hooks.rb:269 0.005
Given a computer 0.294
And I start Tails from USB drive "old" with network unplugged and I login 1:19.663
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 30.810
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.588
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.775
Before features/support/hooks.rb:269 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.559
Then Tails is running from USB drive "old" 0.677
And all tps features are active 2.015
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
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.546
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 4.356
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.418
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.321
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 12.729
And I log in to a new session 18.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.690
And I plug USB drive "to_upgrade" 2.630
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.966
Then the running Tails is installed on USB drive "to_upgrade" 22.099
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.601
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.167
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.134
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.200
And the expected persistent files created with the old Tails version are present in the filesystem 1.869
And all persistent directories from the old Tails version have safe access rights 2.630
After features/support/hooks.rb:326 0.608
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:24.173
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 12.604
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.075
And Tor is ready 21.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.166
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.771
Given I shutdown Tails and wait for the computer to power off 8.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.523
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.289
# 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.246
When the network is plugged 0.123
And Tor is ready 16.732
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.385
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.894
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.495
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.272
When the network is plugged 0.088
And Tor is ready 19.522
Then the Upgrader considers the system as up-to-date 10.772
# 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.622
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.995
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.821
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 9.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 19.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.223
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000