Project Number Date
test_Tails_ISO_stable 5246 04 Nov 2024, 12:40

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:19.276 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:16.971
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.170
When I start Tails from USB drive "old" with network unplugged 1:40.813
Then the boot device has safe access rights 3.628
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.580
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.698
Before features/support/hooks.rb:269 0.004
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:24.241
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 36.051
And I take note of which tps features are available 1.703
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 9.141
After features/support/hooks.rb:326 0.265
After features/support/hooks.rb:100 0.013
Tags: @product
3:5.914
Before features/support/hooks.rb:269 0.008
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.634
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.285
When I write some files expected to persist 1.913
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.765
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.460
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.051
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.007
Tags: @product
2:41.614
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 11.909
And I log in to a new session 21.500
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.340
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.944
Then the running Tails is installed on USB drive "to_upgrade" 23.974
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 2.299
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.929
Before features/support/hooks.rb:269 0.007
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.255
Then all tps features from the old Tails version are active 1.968
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.754
And the expected persistent files created with the old Tails version are present in the filesystem 1.644
And all persistent directories from the old Tails version have safe access rights 2.729
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:4.613
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.240
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
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.513
When the network is plugged 0.086
And Tor is ready 22.899
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.017
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.054
Given I shutdown Tails and wait for the computer to power off 1:32.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.359
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.563
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.301
When the network is plugged 0.084
And Tor is ready 19.769
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.520
Given I shutdown Tails and wait for the computer to power off 6.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.551
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.706
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.460
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.106
And Tor is ready 19.277
Then the Upgrader considers the system as up-to-date 0.327
# 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.447
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.937
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.534
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 12.367
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 17.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.040
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.000