Project Number Date
test_Tails_ISO_devel 3493 26 Aug 2024, 12:43

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 19:43.698 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
1:56.026
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.505
When I start Tails from USB drive "old" with network unplugged 1:20.178
Then the boot device has safe access rights 3.020
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 3.468
After features/support/hooks.rb:100 0.044
Tags: @product
2:3.022
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:20.841
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.770
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.972
And I shutdown Tails and wait for the computer to power off 8.402
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.801
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.584
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.095
When I write some files expected to persist 1.779
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.565
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.391
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.644
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.201
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 11.013
And I log in to a new session 19.714
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.417
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.555
Then the running Tails is installed on USB drive "to_upgrade" 22.512
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:326 2.599
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.631
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.161
Then all tps features from the old Tails version are active 1.775
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.141
And the expected persistent files created with the old Tails version are present in the filesystem 1.673
And all persistent directories from the old Tails version have safe access rights 2.324
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:36.485
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.817
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.339
And Tor is ready 25.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.747
Given I shutdown Tails and wait for the computer to power off 1:18.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.733
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.373
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.294
When the network is plugged 0.073
And Tor is ready 17.898
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.565
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.321
Given I shutdown Tails and wait for the computer to power off 4.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.024
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.067
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.082
And Tor is ready 18.654
Then the Upgrader considers the system as up-to-date 0.309
# 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.804
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.044
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.528
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.769
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.234
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.000