Project Number Date
test_Tails_ISO_devel 3536 08 Oct 2024, 13:08

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:23.447 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:4.857
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.222
When I start Tails from USB drive "old" with network unplugged 1:27.150
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 1.032
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.580
Before features/support/hooks.rb:269 0.007
Given a computer 1.442
And I start Tails from USB drive "old" with network unplugged and I login 1:22.745
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.430
And I take note of which tps features are available 1.322
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.499
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.962
Before features/support/hooks.rb:269 0.008
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.658
Then Tails is running from USB drive "old" 0.967
And all tps features are active 4.436
When I write some files expected to persist 2.560
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.684
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 6.937
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.143
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.657
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 11.224
And I log in to a new session 20.621
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.575
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.247
Then the running Tails is installed on USB drive "to_upgrade" 23.121
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 2.124
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.746
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.371
Then all tps features from the old Tails version are active 1.709
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:36.775
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 13.604
And no SquashFS delta is installed 0.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.117
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.877
Given I shutdown Tails and wait for the computer to power off 10.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.931
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.573
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.228
When the network is plugged 0.081
And Tor is ready 18.665
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.500
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.891
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 2:4.933
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.636
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.063
And Tor is ready 21.410
Then the Upgrader considers the system as up-to-date 0.327
# 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 15.341
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.366
After features/support/hooks.rb:326 1.100
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
38.868
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 11.243
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.107
And the signing key used by the Upgrader is outdated 0.804
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.675
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.000