Project Number Date
test_Tails_ISO_stable 5275 17 Nov 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:31.610 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:3.254
Before features/support/hooks.rb:269 0.004
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.723
When I start Tails from USB drive "old" with network unplugged 1:27.389
Then the boot device has safe access rights 2.901
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.115
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.586
After features/support/hooks.rb:100 0.020
Tags: @product
2:6.182
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:22.696
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 32.626
And I take note of which tps features are available 1.341
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.265
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.977
Before features/support/hooks.rb:269 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.015
Then Tails is running from USB drive "old" 0.749
And all tps features are active 1.787
When I write some files expected to persist 1.705
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 3.081
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.260
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.145
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.652
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.715
And I log in to a new session 18.080
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.704
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.132
Then the running Tails is installed on USB drive "to_upgrade" 23.188
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:326 1.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.312
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.292
Then all tps features from the old Tails version are active 1.519
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 2.922
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.567
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:14.533
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 12.861
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.082
And Tor is ready 25.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.146
Given I shutdown Tails and wait for the computer to power off 8.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.910
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.134
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.402
# 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.403
When the network is plugged 0.067
And Tor is ready 19.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.113
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.631
Given I shutdown Tails and wait for the computer to power off 4.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.303
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.847
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.062
And Tor is ready 18.837
Then the Upgrader considers the system as up-to-date 0.291
# 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.537
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.070
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.697
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.988
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.067
And the signing key used by the Upgrader is outdated 0.728
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.233
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.000