Project Number Date
test_Tails_ISO_devel 3528 02 Oct 2024, 20:56

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:15.649 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.771
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.365
When I start Tails from USB drive "old" with network unplugged 1:26.878
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 10.424
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.676
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:24.574
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 31.936
And I take note of which tps features are available 1.525
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.278
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.007
Tags: @product
2:59.743
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.450
Then Tails is running from USB drive "old" 0.420
And all tps features are active 2.053
When I write some files expected to persist 1.839
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.373
And I take note of which tps features are available 0.405
And I shutdown Tails and wait for the computer to power off 4.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.019
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.145
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 15.283
And I log in to a new session 19.434
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.070
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.991
Then the running Tails is installed on USB drive "to_upgrade" 17.498
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 3.876
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.098
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.060
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.135
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.367
After features/support/hooks.rb:326 0.990
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:30.204
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.134
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.588
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.057
And Tor is ready 22.110
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.171
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.299
Given I shutdown Tails and wait for the computer to power off 10.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.641
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.284
When the network is plugged 0.064
And Tor is ready 19.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.586
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.370
Given I shutdown Tails and wait for the computer to power off 4.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.947
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.618
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.068
And Tor is ready 19.407
Then the Upgrader considers the system as up-to-date 0.299
# 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.002
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.081
After features/support/hooks.rb:326 0.884
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
42.008
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.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.840
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 22.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.993
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.000