Project Number Date
test_Tails_ISO_devel 3273 09 Feb 2024, 19:06

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 18:48.003 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:35.274
Before features/support/hooks.rb:245 0.004
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 19.425
When I start Tails from USB drive "old" with network unplugged 1:10.298
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.403
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 7.076
After features/support/hooks.rb:75 0.007
Tags: @product
2:12.048
Before features/support/hooks.rb:245 0.003
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:16.251
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 44.907
And I take note of which tps features are available 1.540
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.074
After features/support/hooks.rb:291 0.170
After features/support/hooks.rb:75 0.007
Tags: @product
2:42.663
Before features/support/hooks.rb:245 0.002
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.698
Then Tails is running from USB drive "old" 0.362
And all tps features are active 1.877
When I write some files expected to persist 1.708
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
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.419
And I take note of which tps features are available 0.376
And I shutdown Tails and wait for the computer to power off 4.055
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.358
After features/support/hooks.rb:291 0.163
After features/support/hooks.rb:75 0.008
Tags: @product
2:36.864
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.828
And I log in to a new session 23.634
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.356
And I plug USB drive "to_upgrade" 2.531
And I cancel the GNOME authentication prompt 1.940
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.397
Then the running Tails is installed on USB drive "to_upgrade" 14.710
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:291 1.951
After features/support/hooks.rb:75 0.000
Tags: @product
2:25.889
Before features/support/hooks.rb:245 0.005
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.584
Then all tps features from the old Tails version are active 1.610
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.280
And the expected persistent files created with the old Tails version are present in the filesystem 1.329
And all persistent directories from the old Tails version have safe access rights 2.512
After features/support/hooks.rb:291 0.730
After features/support/hooks.rb:75 0.006
Tags: @product @automatic_upgrade
6:41.928
Before features/support/hooks.rb:245 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.733
And no SquashFS delta is installed 0.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
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.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.038
And Tor is ready 18.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.803
Given I shutdown Tails and wait for the computer to power off 7.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.666
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.288
When the network is plugged 0.044
And Tor is ready 16.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.719
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.826
Given I shutdown Tails and wait for the computer to power off 5.483
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.516
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.041
And Tor is ready 14.768
Then the Upgrader considers the system as up-to-date 0.293
# 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 13.741
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.015
After features/support/hooks.rb:291 0.808
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
33.333
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.639
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.493
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 16.282
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.378
After features/support/hooks.rb:291 0.832
After features/support/hooks.rb:75 0.000