Project Number Date
test_Tails_ISO_devel 3582 09 Nov 2024, 12:17

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:48.220 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.384
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.441
When I start Tails from USB drive "old" with network unplugged 1:26.618
Then the boot device has safe access rights 3.054
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.027
Tags: @product
2:4.842
Before features/support/hooks.rb:269 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.088
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 31.823
And I take note of which tps features are available 1.384
Then a Tails persistence partition exists on USB drive "old" 0.763
And I shutdown Tails and wait for the computer to power off 8.271
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.405
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.195
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.896
When I write some files expected to persist 1.733
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.334
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.380
And I take note of which tps features are available 0.393
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.169
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.385
Before features/support/hooks.rb:269 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.263
And I log in to a new session 19.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.946
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.877
Then the running Tails is installed on USB drive "to_upgrade" 20.429
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 1.814
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.994
Before features/support/hooks.rb:269 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.099
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.271
After features/support/hooks.rb:326 0.796
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.873
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.582
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.076
And Tor is ready 22.031
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.480
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.204
Given I shutdown Tails and wait for the computer to power off 10.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.033
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.981
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.305
When the network is plugged 0.083
And Tor is ready 18.174
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.474
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.018
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.936
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.069
And Tor is ready 17.931
Then the Upgrader considers the system as up-to-date 0.346
# 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.050
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.121
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.333
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 1.930
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 20.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.014
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.000