Project Number Date
test_Tails_ISO_devel 3570 31 Oct 2024, 13:10

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 22:37.647 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
3:15.214
Before features/support/hooks.rb:269 0.008
Given a computer 1.520
And I create a 7200 MiB disk named "old" 0.541
And I plug USB drive "old" 1.609
And I write an old version of the Tails USB image to disk "old" 1:3.368
When I start Tails from USB drive "old" with network unplugged 2:2.779
Then the boot device has safe access rights 4.126
And Tails is running from USB drive "old" 0.431
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.391
And I unplug USB drive "old" 0.257
After features/support/hooks.rb:326 7.242
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.342
Before features/support/hooks.rb:269 0.007
Given a computer 0.339
And I start Tails from USB drive "old" with network unplugged and I login 1:30.850
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 33.790
And I take note of which tps features are available 1.696
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.472
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.875
Before features/support/hooks.rb:269 0.005
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.880
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.794
When I write some files expected to persist 1.909
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 2.692
And I take note of which tps features are available 0.627
And I shutdown Tails and wait for the computer to power off 4.196
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.381
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.564
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 24.637
And I log in to a new session 20.621
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.934
And I plug USB drive "to_upgrade" 2.549
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.608
Then the running Tails is installed on USB drive "to_upgrade" 25.687
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 3.841
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.383
Before features/support/hooks.rb:269 0.010
Given a computer 0.282
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.530
Then all tps features from the old Tails version are active 2.290
And Tails is running from USB drive "to_upgrade" 0.462
And the boot device has safe access rights 3.992
And the expected persistent files created with the old Tails version are present in the filesystem 1.767
And all persistent directories from the old Tails version have safe access rights 3.056
After features/support/hooks.rb:326 1.140
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:46.110
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 33.163
And no SquashFS delta is installed 0.255
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.713
When the network is plugged 0.115
And Tor is ready 25.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.333
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.931
Given I shutdown Tails and wait for the computer to power off 11.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.315
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 3.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.418
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.581
When the network is plugged 0.092
And Tor is ready 20.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.137
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.055
Given I shutdown Tails and wait for the computer to power off 4.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.886
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 8.570
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.497
When the network is plugged 0.613
And Tor is ready 22.329
Then the Upgrader considers the system as up-to-date 0.450
# 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 17.337
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.229
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
46.155
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 14.463
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 1.189
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 22.655
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.265
After features/support/hooks.rb:326 1.404
After features/support/hooks.rb:100 0.000