Project Number Date
test_Tails_ISO_devel 3657 22 Jan 2025, 17:48

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 19:51.764 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:56.396
Before features/support/hooks.rb:269 0.002
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 28.143
When I start Tails from USB drive "old" with network unplugged 1:23.075
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 7.027
After features/support/hooks.rb:100 0.006
Tags: @product
2:3.537
Before features/support/hooks.rb:269 0.002
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:21.678
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.666
And I take note of which tps features are available 1.370
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 6.527
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.006
Tags: @product
2:54.211
Before features/support/hooks.rb:269 0.003
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.951
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.070
When I write some files expected to persist 2.074
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.408
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.243
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.873
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.006
Tags: @product
2:40.403
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.538
And I log in to a new session 22.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.059
Then the running Tails is installed on USB drive "to_upgrade" 22.471
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.283
After features/support/hooks.rb:326 3.170
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.229
Before features/support/hooks.rb:269 0.003
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.297
Then all tps features from the old Tails version are active 1.711
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 4.239
And the expected persistent files created with the old Tails version are present in the filesystem 1.584
And all persistent directories from the old Tails version have safe access rights 2.810
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:9.618
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 21.673
And no SquashFS delta is installed 0.246
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.107
And Tor is ready 23.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.793
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.636
Given I shutdown Tails and wait for the computer to power off 8.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.378
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.730
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.321
When the network is plugged 0.080
And Tor is ready 18.998
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.112
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.509
Given I shutdown Tails and wait for the computer to power off 4.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.248
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.747
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.070
And Tor is ready 20.305
Then the Upgrader considers the system as up-to-date 0.348
# 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.145
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.334
After features/support/hooks.rb:326 0.936
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.368
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 12.665
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.170
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.168
And Tor is ready 18.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.521
After features/support/hooks.rb:326 1.391
After features/support/hooks.rb:100 0.000