Project Number Date
test_Tails_ISO_devel 3665 28 Jan 2025, 05:26

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 21:46.736 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:54.830
Before features/support/hooks.rb:269 0.003
Given a computer 0.321
And I create a 7200 MiB disk named "old" 0.098
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 1:10.175
When I start Tails from USB drive "old" with network unplugged 1:38.781
Then the boot device has safe access rights 3.157
And Tails is running from USB drive "old" 0.476
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:326 3.763
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.214
Before features/support/hooks.rb:269 0.002
Given a computer 0.980
And I start Tails from USB drive "old" with network unplugged and I login 1:26.552
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 33.691
And I take note of which tps features are available 1.827
Then a Tails persistence partition exists on USB drive "old" 1.075
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.633
Before features/support/hooks.rb:269 0.003
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.181
Then Tails is running from USB drive "old" 0.557
And all tps features are active 2.439
When I write some files expected to persist 1.882
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.317
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.579
And I shutdown Tails and wait for the computer to power off 4.457
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.962
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.006
Tags: @product
2:57.050
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.303
And I log in to a new session 19.496
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.753
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.064
Then the running Tails is installed on USB drive "to_upgrade" 24.474
And I unplug USB drive "to_upgrade" 0.267
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 7.181
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.372
Before features/support/hooks.rb:269 0.004
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.916
Then all tps features from the old Tails version are active 1.933
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.331
And the expected persistent files created with the old Tails version are present in the filesystem 1.870
And all persistent directories from the old Tails version have safe access rights 2.770
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
7:23.883
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.096
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.736
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.107
And Tor is ready 18.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.144
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.336
Given I shutdown Tails and wait for the computer to power off 11.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.928
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.587
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.156
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.302
When the network is plugged 0.126
And Tor is ready 17.885
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.084
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.241
Given I shutdown Tails and wait for the computer to power off 6.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.773
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.612
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.478
When the network is plugged 0.096
And Tor is ready 48.159
Then the Upgrader considers the system as up-to-date 0.331
# 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.730
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.218
After features/support/hooks.rb:326 0.967
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
42.751
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.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.098
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 20.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.843
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000