Project Number Date
test_Tails_ISO_devel 3576 04 Nov 2024, 13:19

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:58.748 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:15.243
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.489
When I start Tails from USB drive "old" with network unplugged 1:38.270
Then the boot device has safe access rights 3.194
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 3.529
After features/support/hooks.rb:100 0.013
Tags: @product
2:16.093
Before features/support/hooks.rb:269 0.005
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:26.352
Then Tails is running from USB drive "old" 0.391
And I create a persistent partition 37.917
And I take note of which tps features are available 1.714
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.583
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.684
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.124
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.420
When I write some files expected to persist 1.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.698
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 4.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.434
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:41.747
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.586
And I log in to a new session 23.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.317
And I plug USB drive "to_upgrade" 2.547
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.452
Then the running Tails is installed on USB drive "to_upgrade" 23.711
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 2.516
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.628
Before features/support/hooks.rb:269 0.008
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.333
Then all tps features from the old Tails version are active 1.592
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 4.913
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 2.611
After features/support/hooks.rb:326 0.941
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.054
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.753
And no SquashFS delta is installed 0.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.101
And Tor is ready 21.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.488
Given I shutdown Tails and wait for the computer to power off 8.827
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.699
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.355
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.296
When the network is plugged 0.087
And Tor is ready 21.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.497
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.715
Given I shutdown Tails and wait for the computer to power off 6.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.115
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.083
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.064
And Tor is ready 20.210
Then the Upgrader considers the system as up-to-date 0.373
# 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 17.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.994
After features/support/hooks.rb:326 0.791
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
37.296
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.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.135
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 19.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.474
After features/support/hooks.rb:326 0.881
After features/support/hooks.rb:100 0.000