Project Number Date
test_Tails_ISO_devel 3480 14 Aug 2024, 20:50

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:15.451 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:17.725
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 31.438
When I start Tails from USB drive "old" with network unplugged 1:40.716
Then the boot device has safe access rights 3.275
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.554
After features/support/hooks.rb:100 0.013
Tags: @product
2:7.606
Before features/support/hooks.rb:269 0.009
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:23.412
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.750
And I take note of which tps features are available 1.424
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.563
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.014
Tags: @product
2:52.633
Before features/support/hooks.rb:269 0.010
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.250
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.355
When I write some files expected to persist 1.853
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.550
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.418
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.573
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.938
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.578
And I log in to a new session 23.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.446
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.282
Then the running Tails is installed on USB drive "to_upgrade" 19.374
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.682
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.627
Before features/support/hooks.rb:269 0.009
Given a computer 0.288
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.925
Then all tps features from the old Tails version are active 1.606
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.230
And the expected persistent files created with the old Tails version are present in the filesystem 1.726
And all persistent directories from the old Tails version have safe access rights 2.534
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:33.097
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 12.460
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.070
And Tor is ready 19.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.865
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.520
Given I shutdown Tails and wait for the computer to power off 9.117
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.220
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
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.311
# 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.276
When the network is plugged 0.069
And Tor is ready 16.488
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.558
Given I shutdown Tails and wait for the computer to power off 4.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.239
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 4.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.368
When the network is plugged 1.031
And Tor is ready 16.819
Then the Upgrader considers the system as up-to-date 0.369
# 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.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.914
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
36.823
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.670
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.787
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 17.955
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.821
After features/support/hooks.rb:326 0.628
After features/support/hooks.rb:100 0.000