Project Number Date
test_Tails_ISO_devel 3607 09 Dec 2024, 12:39

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:15.149 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.124
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.699
When I start Tails from USB drive "old" with network unplugged 1:26.163
Then the boot device has safe access rights 2.912
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.699
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:24.671
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 30.638
And I take note of which tps features are available 1.847
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.257
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.156
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.880
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.033
When I write some files expected to persist 1.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.320
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 4.139
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.259
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.958
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 11.045
And I log in to a new session 20.262
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.671
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.675
Then the running Tails is installed on USB drive "to_upgrade" 24.546
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.280
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.241
Before features/support/hooks.rb:269 0.006
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.751
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.341
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:54.111
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 32.061
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.437
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.084
And Tor is ready 22.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.688
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.282
Given I shutdown Tails and wait for the computer to power off 1:25.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.425
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.284
When the network is plugged 0.068
And Tor is ready 19.386
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.054
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.489
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.295
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.072
And Tor is ready 19.009
Then the Upgrader considers the system as up-to-date 0.329
# 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 14.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.020
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.857
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 10.300
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.887
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.484
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.000