Project Number Date
test_Tails_ISO_stable 5215 23 Oct 2024, 22:29

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:43.969 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.674
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.782
When I start Tails from USB drive "old" with network unplugged 1:27.323
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 7.698
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.896
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:21.179
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 30.846
And I take note of which tps features are available 1.369
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.231
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.008
Tags: @product
3:4.003
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.162
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.082
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.267
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 4.163
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.949
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.527
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.077
And I log in to a new session 20.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.621
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.803
Then the running Tails is installed on USB drive "to_upgrade" 19.922
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.291
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.334
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.178
Then all tps features from the old Tails version are active 1.791
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 2.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:326 0.969
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:18.836
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.927
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.066
And Tor is ready 16.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.544
Given I shutdown Tails and wait for the computer to power off 8.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.750
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.266
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# 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.417
When the network is plugged 0.081
And Tor is ready 18.254
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.273
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.829
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.870
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.472
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.073
And Tor is ready 20.855
Then the Upgrader considers the system as up-to-date 0.317
# 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.426
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.127
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
34.696
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.368
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
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.843
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.046
After features/support/hooks.rb:326 0.687
After features/support/hooks.rb:100 0.000