Project Number Date
test_Tails_ISO_devel 3586 14 Nov 2024, 12:01

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:24.438 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:3.875
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
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" 29.703
When I start Tails from USB drive "old" with network unplugged 1:29.014
Then the boot device has safe access rights 2.929
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.171
Before features/support/hooks.rb:269 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:21.167
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 29.801
And I take note of which tps features are available 1.433
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 6.453
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.871
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:8.000
Then Tails is running from USB drive "old" 0.328
And all tps features are active 1.843
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.350
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.287
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.288
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.777
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 10.810
And I log in to a new session 19.415
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.850
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.746
Then the running Tails is installed on USB drive "to_upgrade" 21.118
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 2.706
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.997
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.991
Then all tps features from the old Tails version are active 1.516
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.424
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:326 1.097
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.054
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.658
And no SquashFS delta is installed 0.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.058
And Tor is ready 22.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.340
Given I shutdown Tails and wait for the computer to power off 8.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.716
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.952
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.674
# 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.296
When the network is plugged 0.064
And Tor is ready 18.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.222
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.196
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.055
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.403
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.358
When the network is plugged 0.062
And Tor is ready 20.976
Then the Upgrader considers the system as up-to-date 0.297
# 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.029
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.059
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.689
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 10.019
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 1.256
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 18.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.426
After features/support/hooks.rb:326 1.183
After features/support/hooks.rb:100 0.000