Project Number Date
test_Tails_ISO_stable 5346 19 Dec 2024, 08:42

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 18:55.710 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:1.498
Before features/support/hooks.rb:269 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.834
When I start Tails from USB drive "old" with network unplugged 1:26.488
Then the boot device has safe access rights 2.904
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.337
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.458
Before features/support/hooks.rb:269 0.004
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:28.015
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 31.242
And I take note of which tps features are available 1.380
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.421
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.467
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.262
Then Tails is running from USB drive "old" 1.505
And all tps features are active 2.111
When I write some files expected to persist 2.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.354
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.332
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.671
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.731
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.286
And I log in to a new session 19.536
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.503
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.477
Then the running Tails is installed on USB drive "to_upgrade" 24.046
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.161
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.216
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.731
Then all tps features from the old Tails version are active 1.906
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.351
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.294
After features/support/hooks.rb:326 0.867
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:20.023
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.927
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
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.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.067
And Tor is ready 19.803
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.559
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.915
Given I shutdown Tails and wait for the computer to power off 8.861
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.050
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.270
When the network is plugged 0.064
And Tor is ready 19.204
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.643
Given I shutdown Tails and wait for the computer to power off 4.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.968
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.492
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.079
And Tor is ready 19.252
Then the Upgrader considers the system as up-to-date 0.318
# 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.207
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
35.315
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 10.294
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.537
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.775
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.446
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.000