Project Number Date
test_Tails_ISO_devel 3592 19 Nov 2024, 12:51

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 20:31.514 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:9.979
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.667
When I start Tails from USB drive "old" with network unplugged 1:32.693
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.263
After features/support/hooks.rb:326 7.293
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.349
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:23.379
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 32.661
And I take note of which tps features are available 1.592
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.009
Tags: @product
3:13.115
Before features/support/hooks.rb:269 0.005
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.554
Then Tails is running from USB drive "old" 0.473
And all tps features are active 4.067
When I write some files expected to persist 2.413
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 3.128
And I take note of which tps features are available 1.478
And I shutdown Tails and wait for the computer to power off 6.558
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.489
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.427
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.271
And I log in to a new session 22.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.060
And I plug USB drive "to_upgrade" 2.584
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.097
Then the running Tails is installed on USB drive "to_upgrade" 22.435
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.459
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.065
Before features/support/hooks.rb:269 0.006
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.068
Then all tps features from the old Tails version are active 1.497
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.651
And all persistent directories from the old Tails version have safe access rights 2.493
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:13.193
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 13.081
And no SquashFS delta is installed 0.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.730
When the network is plugged 0.187
And Tor is ready 22.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.068
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.203
Given I shutdown Tails and wait for the computer to power off 11.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.826
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.259
When the network is plugged 0.071
And Tor is ready 47.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.581
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.687
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.473
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.470
When the network is plugged 0.073
And Tor is ready 19.843
Then the Upgrader considers the system as up-to-date 0.389
# 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.918
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.078
After features/support/hooks.rb:326 0.940
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.382
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.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.880
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 18.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.072
After features/support/hooks.rb:326 1.401
After features/support/hooks.rb:100 0.000