Project Number Date
test_Tails_ISO_devel 3450 08 Jul 2024, 12:49

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:21.089 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:0.283
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.518
When I start Tails from USB drive "old" with network unplugged 1:26.584
Then the boot device has safe access rights 2.895
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.502
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.400
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:24.310
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 31.213
And I take note of which tps features are available 1.395
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.228
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.031
Before features/support/hooks.rb:269 0.005
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.457
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.414
When I write some files expected to persist 1.827
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.671
And I take note of which tps features are available 0.577
And I shutdown Tails and wait for the computer to power off 4.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.544
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.015
Tags: @product
2:44.925
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.431
And I log in to a new session 17.740
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.593
And I plug USB drive "to_upgrade" 2.602
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.964
Then the running Tails is installed on USB drive "to_upgrade" 20.058
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.268
After features/support/hooks.rb:326 2.575
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.374
Before features/support/hooks.rb:269 0.011
Given a computer 0.815
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.621
Then all tps features from the old Tails version are active 2.091
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:24.343
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.623
And no SquashFS delta is installed 0.255
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.044
And Tor is ready 21.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.592
Given I shutdown Tails and wait for the computer to power off 8.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.744
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.537
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.290
When the network is plugged 0.048
And Tor is ready 15.881
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.278
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.699
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.709
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.325
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.397
When the network is plugged 0.061
And Tor is ready 16.869
Then the Upgrader considers the system as up-to-date 0.307
# 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 13.818
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.095
After features/support/hooks.rb:326 0.788
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
1:3.729
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.729
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.783
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 50.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.664
After features/support/hooks.rb:326 1.455
After features/support/hooks.rb:100 0.000