Project Number Date
test_Tails_ISO_stable 4967 24 Jul 2024, 00:15

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:39.337 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:24.270
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.871
When I start Tails from USB drive "old" with network unplugged 1:48.826
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 8.509
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.066
Before features/support/hooks.rb:269 0.009
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login 1:27.360
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 33.983
And I take note of which tps features are available 1.704
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 9.422
After features/support/hooks.rb:326 0.282
After features/support/hooks.rb:100 0.015
Tags: @product
3:1.757
Before features/support/hooks.rb:269 0.011
Given a computer 0.329
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.030
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.711
When I write some files expected to persist 2.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 3.123
And I take note of which tps features are available 0.528
And I shutdown Tails and wait for the computer to power off 4.651
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.536
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.023
Tags: @product
2:29.512
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.523
And I log in to a new session 17.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.464
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.891
Then the running Tails is installed on USB drive "to_upgrade" 18.045
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 3.529
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.270
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.492
Then all tps features from the old Tails version are active 1.592
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.240
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.877
After features/support/hooks.rb:326 1.185
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:31.079
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.866
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.381
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.061
And Tor is ready 21.160
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.100
Given I shutdown Tails and wait for the computer to power off 8.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.519
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.361
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.443
# 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.270
When the network is plugged 0.031
And Tor is ready 17.469
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.612
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.399
Given I shutdown Tails and wait for the computer to power off 4.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.208
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.449
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.092
And Tor is ready 20.060
Then the Upgrader considers the system as up-to-date 0.394
# 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.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.279
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
51.380
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 24.626
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.010
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 19.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.744
After features/support/hooks.rb:326 1.145
After features/support/hooks.rb:100 0.000