Project Number Date
test_Tails_ISO_stable 5270 16 Nov 2024, 08:41

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:53.508 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:5.410
Before features/support/hooks.rb:269 0.004
Given a computer 0.368
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.398
When I start Tails from USB drive "old" with network unplugged 1:29.358
Then the boot device has safe access rights 3.129
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.529
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.407
Before features/support/hooks.rb:269 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:25.496
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 32.316
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 6.736
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.108
Before features/support/hooks.rb:269 0.008
Given a computer 0.344
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.960
Then Tails is running from USB drive "old" 0.413
And all tps features are active 1.973
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.526
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.540
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.239
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.547
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.411
And I log in to a new session 20.790
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.731
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.923
Then the running Tails is installed on USB drive "to_upgrade" 21.770
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:326 2.238
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.401
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.953
Then all tps features from the old Tails version are active 1.917
And Tails is running from USB drive "to_upgrade" 0.479
And the boot device has safe access rights 3.867
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.559
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:14.860
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 12.211
And no SquashFS delta is installed 0.174
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.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.095
And Tor is ready 49.015
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.736
Given I shutdown Tails and wait for the computer to power off 1:26.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.424
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.550
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.393
When the network is plugged 0.081
And Tor is ready 18.612
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.494
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.210
Given I shutdown Tails and wait for the computer to power off 4.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.246
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.349
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.379
When the network is plugged 0.105
And Tor is ready 19.844
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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.392
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.774
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 10.640
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.588
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.975
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 20.468
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.939
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.000