Project Number Date
test_Tails_ISO_devel 3432 18 Jun 2024, 16:38

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:59.188 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:11.562
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.759
When I start Tails from USB drive "old" with network unplugged 1:34.830
Then the boot device has safe access rights 3.588
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:320 7.009
After features/support/hooks.rb:100 0.012
Tags: @product
2:16.775
Before features/support/hooks.rb:269 0.009
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:31.955
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 33.427
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.419
After features/support/hooks.rb:320 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.936
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.690
Then Tails is running from USB drive "old" 0.379
And all tps features are active 3.616
When I write some files expected to persist 1.789
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.342
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 1.189
And I shutdown Tails and wait for the computer to power off 6.794
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.950
After features/support/hooks.rb:320 0.151
After features/support/hooks.rb:100 0.013
Tags: @product
2:26.995
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.692
And I log in to a new session 18.375
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.123
Then the running Tails is installed on USB drive "to_upgrade" 19.233
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:320 3.778
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.925
Before features/support/hooks.rb:269 0.010
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.251
Then all tps features from the old Tails version are active 1.841
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 2.321
After features/support/hooks.rb:320 0.764
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:24.261
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.646
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.036
And Tor is ready 22.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.303
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.408
Given I shutdown Tails and wait for the computer to power off 8.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.677
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.001
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.275
When the network is plugged 0.038
And Tor is ready 19.935
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.914
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.877
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.680
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.839
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.043
And Tor is ready 17.385
Then the Upgrader considers the system as up-to-date 10.771
# 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.502
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.868
After features/support/hooks.rb:320 0.662
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
35.731
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.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.785
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 19.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.151
After features/support/hooks.rb:320 0.702
After features/support/hooks.rb:100 0.000