Project Number Date
test_Tails_ISO_stable 5096 12 Sep 2024, 12:36

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:29.265 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:9.704
Before features/support/hooks.rb:269 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.248
When I start Tails from USB drive "old" with network unplugged 1:34.156
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.024
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.482
Before features/support/hooks.rb:269 0.005
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:19.594
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 30.646
And I take note of which tps features are available 1.347
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.554
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.251
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.905
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.751
When I write some files expected to persist 1.592
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.666
And I take note of which tps features are available 0.378
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.571
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.745
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.538
And I log in to a new session 20.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.815
And I plug USB drive "to_upgrade" 2.505
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.198
Then the running Tails is installed on USB drive "to_upgrade" 19.892
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.737
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.323
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.482
Then all tps features from the old Tails version are active 1.756
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.964
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.238
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:14.098
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 11.823
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.068
And Tor is ready 20.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.518
Given I shutdown Tails and wait for the computer to power off 10.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.039
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.047
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
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.418
# 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.287
When the network is plugged 0.069
And Tor is ready 19.240
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.550
Given I shutdown Tails and wait for the computer to power off 4.193
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.850
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.994
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.482
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.064
And Tor is ready 18.072
Then the Upgrader considers the system as up-to-date 0.330
# 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 13.618
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.072
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.660
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.803
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.789
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.467
After features/support/hooks.rb:326 0.878
After features/support/hooks.rb:100 0.000