Project Number Date
test_Tails_ISO_devel 3641 09 Jan 2025, 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 19:0.270 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:2.261
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.749
When I start Tails from USB drive "old" with network unplugged 1:27.057
Then the boot device has safe access rights 3.108
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 6.931
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.801
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:25.913
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.660
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 6.552
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.421
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.928
Then Tails is running from USB drive "old" 0.314
And all tps features are active 2.073
When I write some files expected to persist 2.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.829
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.392
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.287
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.007
Tags: @product
2:27.714
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.041
And I log in to a new session 19.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.638
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.830
Then the running Tails is installed on USB drive "to_upgrade" 19.721
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 2.651
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.159
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.002
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 3.063
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.311
After features/support/hooks.rb:326 0.644
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:11.128
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.280
And no SquashFS delta is installed 0.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.078
And Tor is ready 22.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.306
Given I shutdown Tails and wait for the computer to power off 8.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.339
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.015
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.303
When the network is plugged 0.087
And Tor is ready 19.673
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.122
Given I shutdown Tails and wait for the computer to power off 4.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.023
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.909
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.076
And Tor is ready 18.691
Then the Upgrader considers the system as up-to-date 0.303
# 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.885
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.982
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:1.782
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.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 49.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.000