Project Number Date
test_Tails_ISO_stable 5213 23 Oct 2024, 12:50

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 18:52.981 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.250
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 28.868
When I start Tails from USB drive "old" with network unplugged 1:27.778
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.378
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:326 3.564
After features/support/hooks.rb:100 0.023
Tags: @product
2:7.048
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:22.444
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 33.137
And I take note of which tps features are available 1.462
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 8.567
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.679
Before features/support/hooks.rb:269 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.343
Then Tails is running from USB drive "old" 1.253
And all tps features are active 2.178
When I write some files expected to persist 1.854
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.101
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.404
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.190
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.593
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 10.350
And I log in to a new session 22.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.612
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.582
Then the running Tails is installed on USB drive "to_upgrade" 21.016
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.695
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.328
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.533
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.105
And the expected persistent files created with the old Tails version are present in the filesystem 1.395
And all persistent directories from the old Tails version have safe access rights 3.169
After features/support/hooks.rb:326 0.845
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:32.036
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 11.980
And no SquashFS delta is installed 0.513
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.070
And Tor is ready 22.167
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.301
Given I shutdown Tails and wait for the computer to power off 8.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.465
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.588
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.286
When the network is plugged 0.070
And Tor is ready 20.665
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.303
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.200
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.019
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.076
And Tor is ready 19.825
Then the Upgrader considers the system as up-to-date 0.360
# 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.131
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.044
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 9.516
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.848
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.014
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.000