Project Number Date
test_Tails_ISO_devel 3443 01 Jul 2024, 13:56

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:52.919 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:16.441
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.782
When I start Tails from USB drive "old" with network unplugged 1:41.454
Then the boot device has safe access rights 2.869
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.026
Tags: @product
2:0.812
Before features/support/hooks.rb:269 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:19.259
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 30.374
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.269
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.487
Before features/support/hooks.rb:269 0.007
Given a computer 0.314
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.733
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.010
When I write some files expected to persist 1.663
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 2.574
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.663
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.984
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.411
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.692
And I log in to a new session 16.842
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.356
And I plug USB drive "to_upgrade" 2.331
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.728
Then the running Tails is installed on USB drive "to_upgrade" 19.047
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 1.918
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.972
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.820
Then all tps features from the old Tails version are active 1.538
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.297
And the expected persistent files created with the old Tails version are present in the filesystem 1.347
And all persistent directories from the old Tails version have safe access rights 2.457
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:38.103
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.393
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
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.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.038
And Tor is ready 22.515
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.142
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.319
Given I shutdown Tails and wait for the computer to power off 8.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.948
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# 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.243
When the network is plugged 0.050
And Tor is ready 16.985
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.860
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.373
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.616
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.934
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.037
And Tor is ready 47.655
Then the Upgrader considers the system as up-to-date 0.306
# 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 13.731
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.963
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.689
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 14.417
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.792
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.845
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 16.370
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.135
After features/support/hooks.rb:326 1.292
After features/support/hooks.rb:100 0.000