Project Number Date
test_Tails_ISO_disable-thunderbird-telemetry 5 15 Nov 2024, 14:29

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:26.020 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:18.126
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.079
When I start Tails from USB drive "old" with network unplugged 1:39.364
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.421
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.594
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.379
Before features/support/hooks.rb:269 0.007
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login 1:24.321
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 35.782
And I take note of which tps features are available 1.406
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.486
After features/support/hooks.rb:326 0.215
After features/support/hooks.rb:100 0.017
Tags: @product
2:56.517
Before features/support/hooks.rb:269 0.008
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.315
Then Tails is running from USB drive "old" 0.791
And all tps features are active 1.958
When I write some files expected to persist 1.879
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.576
And all persistent directories from the old Tails version have safe access rights 2.964
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.354
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.571
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.432
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.456
And I log in to a new session 18.901
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.997
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.792
Then the running Tails is installed on USB drive "to_upgrade" 20.415
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 0.939
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.995
Before features/support/hooks.rb:269 0.006
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.197
Then all tps features from the old Tails version are active 1.594
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.195
And the expected persistent files created with the old Tails version are present in the filesystem 1.528
And all persistent directories from the old Tails version have safe access rights 2.883
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:29.085
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 13.613
And no SquashFS delta is installed 0.556
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.082
And Tor is ready 20.566
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.797
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.836
Given I shutdown Tails and wait for the computer to power off 11.039
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.106
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.254
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.322
When the network is plugged 0.071
And Tor is ready 18.147
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.580
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.157
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.503
When the network is plugged 0.086
And Tor is ready 19.236
Then the Upgrader considers the system as up-to-date 0.336
# 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 14.468
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.178
After features/support/hooks.rb:326 0.840
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.482
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.659
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.773
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.798
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.000