Project Number Date
test_Tails_ISO_devel 3516 21 Sep 2024, 15:24

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 20:6.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
2:9.098
Before features/support/hooks.rb:269 0.009
Given a computer 0.255
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.712
When I start Tails from USB drive "old" with network unplugged 1:29.167
Then the boot device has safe access rights 3.748
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 4.127
After features/support/hooks.rb:100 0.012
Tags: @product
2:24.042
Before features/support/hooks.rb:269 0.008
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:27.983
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 43.908
And I take note of which tps features are available 2.214
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 8.569
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.284
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.577
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.952
When I write some files expected to persist 2.089
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.302
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.801
And I take note of which tps features are available 2.013
And I shutdown Tails and wait for the computer to power off 6.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.110
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.609
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 12.771
And I log in to a new session 20.661
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.388
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.921
Then the running Tails is installed on USB drive "to_upgrade" 23.900
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.272
After features/support/hooks.rb:326 2.345
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.694
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.678
Then all tps features from the old Tails version are active 2.141
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.529
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:52.398
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.205
And no SquashFS delta is installed 0.092
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.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.587
When the network is plugged 0.449
And Tor is ready 20.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.908
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.770
Given I shutdown Tails and wait for the computer to power off 10.880
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.606
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.838
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
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.318
# 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.350
When the network is plugged 0.088
And Tor is ready 20.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.309
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.793
Given I shutdown Tails and wait for the computer to power off 4.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.160
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.403
When the network is plugged 0.098
And Tor is ready 16.863
Then the Upgrader considers the system as up-to-date 0.332
# 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.943
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.237
After features/support/hooks.rb:326 0.838
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.360
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.037
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.728
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.641
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.000