Project Number Date
test_Tails_ISO_stable 4934 11 Jul 2024, 22:16

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:22.310 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:23.890
Before features/support/hooks.rb:269 0.008
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.044
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:46.917
Then the boot device has safe access rights 3.258
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.703
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.286
Before features/support/hooks.rb:269 0.005
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:35.761
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 31.740
And I take note of which tps features are available 1.718
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.536
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.748
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.051
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.132
When I write some files expected to persist 1.977
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.306
And all persistence configuration files have safe access rights 0.639
And all persistent directories from the old Tails version have safe access rights 2.612
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.601
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.323
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.295
And I log in to a new session 20.160
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.795
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.965
Then the running Tails is installed on USB drive "to_upgrade" 18.177
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 4.217
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.675
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.547
Then all tps features from the old Tails version are active 1.917
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.747
After features/support/hooks.rb:326 1.082
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:21.551
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.260
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.458
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.603
When the network is plugged 0.057
And Tor is ready 22.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.712
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.593
Given I shutdown Tails and wait for the computer to power off 10.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.219
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.316
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.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.312
When the network is plugged 0.039
And Tor is ready 18.778
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.858
Given I shutdown Tails and wait for the computer to power off 4.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.520
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.440
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.385
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.055
And Tor is ready 20.260
Then the Upgrader considers the system as up-to-date 0.344
# 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.530
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.833
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.959
But a current signing key is available on our website 0.000
When the network is plugged 0.174
And Tor is ready 18.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.472
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000