Project Number Date
test_Tails_ISO_disable-thunderbird-telemetry 7 17 Nov 2024, 02:09

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 18:26.820 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:1.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.763
When I start Tails from USB drive "old" with network unplugged 1:24.604
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 7.033
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.597
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:20.446
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.993
And I take note of which tps features are available 1.599
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.263
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.336
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.057
Then Tails is running from USB drive "old" 1.084
And all tps features are active 2.009
When I write some files expected to persist 2.805
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.900
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 4.296
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.040
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.887
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 10.504
And I log in to a new session 19.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.835
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.721
Then the running Tails is installed on USB drive "to_upgrade" 23.319
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.563
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.335
Before features/support/hooks.rb:269 0.006
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.410
Then all tps features from the old Tails version are active 1.528
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.643
And all persistent directories from the old Tails version have safe access rights 2.272
After features/support/hooks.rb:326 0.992
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:7.145
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.161
And no SquashFS delta is installed 0.454
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.860
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.075
And Tor is ready 19.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.517
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.219
Given I shutdown Tails and wait for the computer to power off 10.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.298
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.089
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.264
When the network is plugged 0.075
And Tor is ready 17.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.244
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.636
Given I shutdown Tails and wait for the computer to power off 4.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.747
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.800
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.456
When the network is plugged 0.060
And Tor is ready 16.478
Then the Upgrader considers the system as up-to-date 0.292
# 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.727
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.115
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.659
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 0.795
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 20.244
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.661
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000