Project Number Date
test_Tails_ISO_devel 3672 29 Jan 2025, 19:58

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:16.111 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
1:59.639
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.196
When I start Tails from USB drive "old" with network unplugged 1:23.287
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 7.001
After features/support/hooks.rb:100 0.005
Tags: @product
2:3.760
Before features/support/hooks.rb:269 0.003
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:21.038
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.869
And I take note of which tps features are available 1.299
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.006
Tags: @product
2:42.408
Before features/support/hooks.rb:269 0.003
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.819
Then Tails is running from USB drive "old" 1.218
And all tps features are active 1.883
When I write some files expected to persist 1.570
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
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.329
And I take note of which tps features are available 0.381
And I shutdown Tails and wait for the computer to power off 4.447
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.026
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.774
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 9.960
And I log in to a new session 18.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.350
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.839
Then the running Tails is installed on USB drive "to_upgrade" 17.081
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 6.910
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.983
Before features/support/hooks.rb:269 0.003
Given a computer 0.152
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.055
Then all tps features from the old Tails version are active 1.512
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.264
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.268
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:17.838
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.298
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.070
And Tor is ready 20.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.088
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.154
Given I shutdown Tails and wait for the computer to power off 8.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.847
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.046
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.341
When the network is plugged 0.066
And Tor is ready 18.932
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.711
Given I shutdown Tails and wait for the computer to power off 4.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.015
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.843
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.096
And Tor is ready 18.820
Then the Upgrader considers the system as up-to-date 0.285
# 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 15.594
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.883
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
32.708
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.774
After features/support/hooks.rb:326 0.864
After features/support/hooks.rb:100 0.000