Project Number Date
test_Tails_ISO_20522-ocr-more 48 31 Jan 2025, 05:16

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:13.008 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:56.270
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.021
When I start Tails from USB drive "old" with network unplugged 1:20.996
Then the boot device has safe access rights 3.006
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 6.724
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.900
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:21.031
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 30.534
And I take note of which tps features are available 1.380
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.518
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.990
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.852
Then Tails is running from USB drive "old" 0.554
And all tps features are active 1.925
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.709
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.636
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.069
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.368
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.468
And I log in to a new session 18.582
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.459
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.728
Then the running Tails is installed on USB drive "to_upgrade" 17.320
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 3.583
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.789
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.248
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.725
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:326 0.888
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:20.081
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.533
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.607
When the network is plugged 0.068
And Tor is ready 20.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.329
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.589
Given I shutdown Tails and wait for the computer to power off 8.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.034
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.295
# 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.260
When the network is plugged 0.088
And Tor is ready 15.384
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.173
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.476
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.074
And Tor is ready 16.878
Then the Upgrader considers the system as up-to-date 0.310
# 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.581
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.880
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
31.608
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 9.589
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.124
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 16.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.977
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000