Project Number Date
test_Tails_ISO_20522-ocr-more 41 26 Jan 2025, 05:13

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:34.272 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.323
Before features/support/hooks.rb:269 0.004
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.400
When I start Tails from USB drive "old" with network unplugged 1:36.614
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.789
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:21.190
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 33.464
And I take note of which tps features are available 1.538
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.223
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.802
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.941
When I write some files expected to persist 1.659
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.606
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.637
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.922
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.457
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 10.271
And I log in to a new session 19.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.424
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.691
Then the running Tails is installed on USB drive "to_upgrade" 16.513
And I unplug USB drive "to_upgrade" 0.277
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.519
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.712
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.591
Then all tps features from the old Tails version are active 1.434
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.490
And the expected persistent files created with the old Tails version are present in the filesystem 1.356
And all persistent directories from the old Tails version have safe access rights 2.320
After features/support/hooks.rb:326 0.926
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:26.869
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.177
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.070
And Tor is ready 19.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.306
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.955
Given I shutdown Tails and wait for the computer to power off 8.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.493
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.069
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
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.324
# 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.327
When the network is plugged 0.084
And Tor is ready 20.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.930
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.927
Given I shutdown Tails and wait for the computer to power off 4.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.310
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.984
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.080
And Tor is ready 19.282
Then the Upgrader considers the system as up-to-date 0.289
# 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.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
35.895
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 10.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 18.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.647
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.000