Project Number Date
test_Tails_ISO_devel 3706 22 Feb 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 20:15.372 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.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.158
When I start Tails from USB drive "old" with network unplugged 1:27.046
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.479
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:23.923
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 31.584
And I take note of which tps features are available 1.506
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.490
After features/support/hooks.rb:330 0.307
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.024
Then Tails is running from USB drive "old" 1.601
And all tps features are active 1.982
When I write some files expected to persist 1.878
# 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.434
And all persistent directories from the old Tails version have safe access rights 2.816
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 4.512
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.674
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.270
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.356
And I log in to a new session 19.003
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.388
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.155
Then the running Tails is installed on USB drive "to_upgrade" 21.251
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.299
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.660
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.982
Then all tps features from the old Tails version are active 1.537
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.522
After features/support/hooks.rb:330 1.357
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:47.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.120
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.084
And Tor is ready 26.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.289
Given I shutdown Tails and wait for the computer to power off 11.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.353
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.421
And only the 6.2~testoverlayfs SquashFS delta is installed 0.142
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.368
# 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.284
When the network is plugged 0.076
And Tor is ready 20.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.509
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.346
Given I shutdown Tails and wait for the computer to power off 1:1.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.341
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.417
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.100
And Tor is ready 21.344
Then the Upgrader considers the system as up-to-date 0.314
# 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 16.528
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.437
After features/support/hooks.rb:330 0.941
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
41.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.974
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.137
After features/support/hooks.rb:330 0.834
After features/support/hooks.rb:100 0.000