Project Number Date
test_Tails_ISO_devel 3601 03 Dec 2024, 12: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 21:59.843 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
3:18.356
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 1:17.423
When I start Tails from USB drive "old" with network unplugged 1:55.208
Then the boot device has safe access rights 3.230
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 3.761
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.053
Before features/support/hooks.rb:269 0.006
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login 1:28.269
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 32.369
And I take note of which tps features are available 1.978
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.832
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.014
Tags: @product
3:9.655
Before features/support/hooks.rb:269 0.011
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.987
Then Tails is running from USB drive "old" 0.439
And all tps features are active 2.458
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.852
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 4.076
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.562
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.011
Tags: @product
2:39.958
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.340
And I log in to a new session 21.034
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.263
And I plug USB drive "to_upgrade" 2.609
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.463
Then the running Tails is installed on USB drive "to_upgrade" 23.784
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:326 1.996
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.621
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.936
Then all tps features from the old Tails version are active 1.857
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.859
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.826
After features/support/hooks.rb:326 2.049
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:28.072
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 14.041
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.741
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.069
And Tor is ready 24.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.774
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.010
Given I shutdown Tails and wait for the computer to power off 11.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.063
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.617
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.327
When the network is plugged 0.067
And Tor is ready 47.477
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.624
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.954
Given I shutdown Tails and wait for the computer to power off 5.072
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.637
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.394
When the network is plugged 0.709
And Tor is ready 16.999
Then the Upgrader considers the system as up-to-date 10.886
# 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.799
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.071
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
43.125
Before features/support/hooks.rb:269 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.332
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 1.248
But a current signing key is available on our website 0.000
When the network is plugged 0.132
And Tor is ready 21.757
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.108
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.000