Project Number Date
test_Tails_ISO_stable 5255 08 Nov 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 19:58.918 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:30.297
Before features/support/hooks.rb:269 0.006
Given a computer 0.303
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.475
When I start Tails from USB drive "old" with network unplugged 1:52.247
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.785
Before features/support/hooks.rb:269 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:24.307
Then Tails is running from USB drive "old" 0.452
And I create a persistent partition 32.070
And I take note of which tps features are available 1.511
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.007
Tags: @product
3:0.944
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.221
Then Tails is running from USB drive "old" 0.308
And all tps features are active 2.393
When I write some files expected to persist 1.770
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.763
And I take note of which tps features are available 0.873
And I shutdown Tails and wait for the computer to power off 4.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.395
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.284
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.673
And I log in to a new session 21.770
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.769
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.992
Then the running Tails is installed on USB drive "to_upgrade" 23.240
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.768
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.903
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.917
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.764
And the expected persistent files created with the old Tails version are present in the filesystem 1.478
And all persistent directories from the old Tails version have safe access rights 2.449
After features/support/hooks.rb:326 0.648
After features/support/hooks.rb:100 0.065
Tags: @product @automatic_upgrade
6:48.451
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 25.535
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.073
And Tor is ready 23.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.066
Given I shutdown Tails and wait for the computer to power off 8.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.718
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.594
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.298
When the network is plugged 0.079
And Tor is ready 22.546
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.978
Given I shutdown Tails and wait for the computer to power off 4.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.210
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.152
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.069
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.080
And Tor is ready 20.722
Then the Upgrader considers the system as up-to-date 0.357
# 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.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.986
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
40.251
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.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.757
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 20.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.125
After features/support/hooks.rb:326 0.677
After features/support/hooks.rb:100 0.000