Project Number Date
test_Tails_ISO_devel 3644 11 Jan 2025, 17:48

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:31.379 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:5.606
Before features/support/hooks.rb:269 0.003
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.604
When I start Tails from USB drive "old" with network unplugged 1:28.906
Then the boot device has safe access rights 2.861
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.005
Tags: @product
1:59.660
Before features/support/hooks.rb:269 0.002
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:20.323
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 30.635
And I take note of which tps features are available 1.164
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 6.289
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.007
Tags: @product
2:48.958
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.188
Then Tails is running from USB drive "old" 0.367
And all tps features are active 2.031
When I write some files expected to persist 2.038
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.446
And I take note of which tps features are available 0.537
And I shutdown Tails and wait for the computer to power off 4.680
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.831
After features/support/hooks.rb:326 0.090
After features/support/hooks.rb:100 0.005
Tags: @product
2:31.555
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.947
And I log in to a new session 19.401
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.362
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.458
Then the running Tails is installed on USB drive "to_upgrade" 22.371
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.129
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.220
Before features/support/hooks.rb:269 0.002
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.548
Then all tps features from the old Tails version are active 1.547
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.222
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.159
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:9.553
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.151
And no SquashFS delta is installed 0.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.962
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.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.066
And Tor is ready 23.108
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.424
Given I shutdown Tails and wait for the computer to power off 8.666
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.536
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.264
When the network is plugged 0.076
And Tor is ready 19.623
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.820
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.467
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.138
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.999
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.334
When the network is plugged 0.085
And Tor is ready 17.765
Then the Upgrader considers the system as up-to-date 0.302
# 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.039
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.906
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
40.823
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.869
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 23.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.429
After features/support/hooks.rb:326 0.699
After features/support/hooks.rb:100 0.000