Project Number Date
test_Tails_ISO_stable 4927 10 Jul 2024, 12: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:1.488 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:58.998
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 29.941
When I start Tails from USB drive "old" with network unplugged 1:24.020
Then the boot device has safe access rights 2.873
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.267
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.381
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:27.314
Then Tails is running from USB drive "old" 0.951
And I create a persistent partition 30.509
And I take note of which tps features are available 1.376
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.267
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.982
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.704
Then Tails is running from USB drive "old" 0.300
And all tps features are active 1.835
When I write some files expected to persist 1.498
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.576
And I take note of which tps features are available 0.440
And I shutdown Tails and wait for the computer to power off 4.140
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.700
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.334
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.015
And I log in to a new session 16.538
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.445
And I plug USB drive "to_upgrade" 2.343
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.586
Then the running Tails is installed on USB drive "to_upgrade" 16.021
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:326 6.580
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.059
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.271
Then all tps features from the old Tails version are active 1.517
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.027
And the expected persistent files created with the old Tails version are present in the filesystem 1.511
And all persistent directories from the old Tails version have safe access rights 2.235
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:12.072
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.307
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.046
And Tor is ready 19.478
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.190
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.390
Given I shutdown Tails and wait for the computer to power off 8.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.150
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.984
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.131
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.455
# 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.269
When the network is plugged 0.035
And Tor is ready 15.887
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.118
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.361
Given I shutdown Tails and wait for the computer to power off 4.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.295
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.864
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.030
And Tor is ready 20.524
Then the Upgrader considers the system as up-to-date 0.312
# 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.631
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.862
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
31.660
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 9.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 1.012
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 14.591
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.225
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.000