Project Number Date
test_Tails_ISO_devel 3434 20 Jun 2024, 12:22

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:29.907 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:27.678
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.120
When I start Tails from USB drive "old" with network unplugged 1:52.676
Then the boot device has safe access rights 2.681
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.087
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 3.485
After features/support/hooks.rb:100 0.010
Tags: @product
2:0.804
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:18.405
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.327
And I take note of which tps features are available 1.400
Then a Tails persistence partition exists on USB drive "old" 0.745
And I shutdown Tails and wait for the computer to power off 8.411
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.609
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.676
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.927
When I write some files expected to persist 1.583
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.379
And I shutdown Tails and wait for the computer to power off 4.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.157
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.497
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.660
And I log in to a new session 16.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.558
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.041
Then the running Tails is installed on USB drive "to_upgrade" 15.536
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 3.495
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.403
Before features/support/hooks.rb:269 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.637
Then all tps features from the old Tails version are active 1.508
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.836
And the expected persistent files created with the old Tails version are present in the filesystem 1.531
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:326 0.627
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:15.387
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.675
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.040
And Tor is ready 21.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.054
Given I shutdown Tails and wait for the computer to power off 8.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.156
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.269
When the network is plugged 0.031
And Tor is ready 18.548
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.343
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.743
Given I shutdown Tails and wait for the computer to power off 4.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.360
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.803
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.042
And Tor is ready 18.209
Then the Upgrader considers the system as up-to-date 10.761
# 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.902
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.867
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.525
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 9.968
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.825
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 19.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.946
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.000