Project Number Date
test_Tails_ISO_stable 4994 02 Aug 2024, 12:31

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:23.575 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:14.985
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 33.992
When I start Tails from USB drive "old" with network unplugged 1:35.399
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.775
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.552
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:23.471
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 30.348
And I take note of which tps features are available 1.726
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.608
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.013
Tags: @product
2:51.786
Before features/support/hooks.rb:269 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.160
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.051
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.419
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.572
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.398
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.290
And I log in to a new session 19.640
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.366
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.898
Then the running Tails is installed on USB drive "to_upgrade" 19.334
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.132
Before features/support/hooks.rb:269 0.008
Given a computer 0.283
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.152
Then all tps features from the old Tails version are active 1.692
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.485
And all persistent directories from the old Tails version have safe access rights 2.728
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:50.026
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 11.059
And no SquashFS delta is installed 0.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.596
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.014
When the network is plugged 0.153
And Tor is ready 21.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.335
Given I shutdown Tails and wait for the computer to power off 10.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.584
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.191
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.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.037
And Tor is ready 20.690
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.810
Given I shutdown Tails and wait for the computer to power off 1:8.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.488
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.384
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.042
And Tor is ready 19.074
Then the Upgrader considers the system as up-to-date 0.364
# 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.088
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.966
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.693
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 9.460
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.769
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 22.359
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.611
After features/support/hooks.rb:326 0.923
After features/support/hooks.rb:100 0.000