Project Number Date
test_Tails_ISO_devel 3649 16 Jan 2025, 00:38

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 21:48.338 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
3:7.451
Before features/support/hooks.rb:269 0.002
Given a computer 1.511
And I create a 7200 MiB disk named "old" 0.426
And I plug USB drive "old" 1.236
And I write an old version of the Tails USB image to disk "old" 1:15.908
When I start Tails from USB drive "old" with network unplugged 1:43.928
Then the boot device has safe access rights 3.460
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.756
After features/support/hooks.rb:100 0.006
Tags: @product
2:19.752
Before features/support/hooks.rb:269 0.003
Given a computer 0.855
And I start Tails from USB drive "old" with network unplugged and I login 1:36.547
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.810
And I take note of which tps features are available 1.969
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 6.391
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.007
Tags: @product
3:4.288
Before features/support/hooks.rb:269 0.002
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.159
Then Tails is running from USB drive "old" 1.285
And all tps features are active 2.742
When I write some files expected to persist 3.544
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.868
And I take note of which tps features are available 0.638
And I shutdown Tails and wait for the computer to power off 4.269
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.836
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.006
Tags: @product
3:1.010
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.652
And I log in to a new session 23.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.871
And I plug USB drive "to_upgrade" 2.628
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.552
Then the running Tails is installed on USB drive "to_upgrade" 22.811
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 4.204
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.933
Before features/support/hooks.rb:269 0.003
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.477
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.751
And all persistent directories from the old Tails version have safe access rights 2.873
After features/support/hooks.rb:326 1.010
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:44.454
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.786
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
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.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.086
And Tor is ready 21.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.146
Given I shutdown Tails and wait for the computer to power off 8.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.526
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.400
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.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.279
When the network is plugged 0.083
And Tor is ready 18.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.106
Given I shutdown Tails and wait for the computer to power off 4.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.532
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.096
And Tor is ready 21.539
Then the Upgrader considers the system as up-to-date 0.322
# 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 15.253
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.114
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
1:0.447
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 49.376
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.000