Project Number Date
test_Tails_ISO_stable 4972 25 Jul 2024, 08:24

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:43.183 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:23.675
Before features/support/hooks.rb:269 0.009
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 35.518
When I start Tails from USB drive "old" with network unplugged 1:42.167
Then the boot device has safe access rights 3.551
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.851
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.341
Before features/support/hooks.rb:269 0.007
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:26.950
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 34.004
And I take note of which tps features are available 1.598
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 6.421
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.409
Before features/support/hooks.rb:269 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.624
Then Tails is running from USB drive "old" 0.408
And all tps features are active 1.996
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.578
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.510
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.939
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.326
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.222
And I log in to a new session 19.729
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.884
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.907
Then the running Tails is installed on USB drive "to_upgrade" 20.742
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.248
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.085
Before features/support/hooks.rb:269 0.009
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.692
Then all tps features from the old Tails version are active 1.618
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.405
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.463
After features/support/hooks.rb:326 1.048
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:41.461
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 27.793
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.048
And Tor is ready 20.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.236
Given I shutdown Tails and wait for the computer to power off 8.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.209
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.168
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.263
When the network is plugged 0.037
And Tor is ready 21.330
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.094
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.181
Given I shutdown Tails and wait for the computer to power off 4.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.715
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.197
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.040
And Tor is ready 20.607
Then the Upgrader considers the system as up-to-date 0.355
# 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.547
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.884
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.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.744
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 17.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.185
After features/support/hooks.rb:326 1.387
After features/support/hooks.rb:100 0.000