Project Number Date
test_Tails_ISO_20522-ocr-more 38 23 Jan 2025, 05:21

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:54.608 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:7.558
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.450
When I start Tails from USB drive "old" with network unplugged 1:25.790
Then the boot device has safe access rights 3.039
And Tails is running from USB drive "old" 0.322
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.318
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.288
Before features/support/hooks.rb:269 0.005
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:25.852
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 30.523
And I take note of which tps features are available 1.308
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 6.204
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.489
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.552
Then Tails is running from USB drive "old" 0.425
And all tps features are active 2.143
When I write some files expected to persist 1.814
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.876
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.146
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.012
Tags: @product
2:27.723
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 10.204
And I log in to a new session 19.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.903
Then the running Tails is installed on USB drive "to_upgrade" 18.817
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 3.070
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.508
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.747
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.559
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
6:30.579
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.799
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.596
When the network is plugged 0.114
And Tor is ready 23.521
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.165
Given I shutdown Tails and wait for the computer to power off 12.864
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.205
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.379
# 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.328
When the network is plugged 0.080
And Tor is ready 19.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.657
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.439
Given I shutdown Tails and wait for the computer to power off 4.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.331
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.087
And Tor is ready 18.231
Then the Upgrader considers the system as up-to-date 0.346
# 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.934
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.987
After features/support/hooks.rb:326 0.719
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.460
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.510
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.102
After features/support/hooks.rb:326 2.050
After features/support/hooks.rb:100 0.000