Project Number Date
test_Tails_ISO_stable 5191 17 Oct 2024, 12:42

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 19:56.954 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:38.448
Before features/support/hooks.rb:269 0.003
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 51.757
When I start Tails from USB drive "old" with network unplugged 1:41.012
Then the boot device has safe access rights 3.228
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.721
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.910
Before features/support/hooks.rb:269 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:22.331
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 32.349
And I take note of which tps features are available 1.640
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.229
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.481
Before features/support/hooks.rb:269 0.003
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.480
Then Tails is running from USB drive "old" 0.307
And all tps features are active 4.230
When I write some files expected to persist 1.900
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.280
And I take note of which tps features are available 0.526
And I shutdown Tails and wait for the computer to power off 4.456
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.411
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.581
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.941
And I log in to a new session 18.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.647
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.228
Then the running Tails is installed on USB drive "to_upgrade" 21.181
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.039
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.648
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.088
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 2.510
After features/support/hooks.rb:326 0.653
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:53.204
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 13.289
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.642
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.065
And Tor is ready 25.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.640
Given I shutdown Tails and wait for the computer to power off 10.633
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.580
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.899
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.400
When the network is plugged 0.068
And Tor is ready 46.765
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.109
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.138
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.005
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.094
And Tor is ready 16.338
Then the Upgrader considers the system as up-to-date 0.351
# 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.108
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.239
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.680
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 11.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.718
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 1.157
But a current signing key is available on our website 0.000
When the network is plugged 0.148
And Tor is ready 18.455
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.984
After features/support/hooks.rb:326 2.557
After features/support/hooks.rb:100 0.000