Project Number Date
test_Tails_ISO_stable 4839 14 May 2024, 12:32

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:18.153 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:13.367
Before features/support/hooks.rb:259 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.839
When I start Tails from USB drive "old" with network unplugged 1:34.016
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:305 11.823
After features/support/hooks.rb:89 0.013
Tags: @product
2:13.355
Before features/support/hooks.rb:259 0.008
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:23.736
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 38.075
And I take note of which tps features are available 1.814
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.352
After features/support/hooks.rb:305 0.176
After features/support/hooks.rb:89 0.011
Tags: @product
2:52.416
Before features/support/hooks.rb:259 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.111
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.107
When I write some files expected to persist 1.640
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.495
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.227
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.156
After features/support/hooks.rb:305 0.107
After features/support/hooks.rb:89 0.010
Tags: @product
2:38.202
Before features/support/hooks.rb:259 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 24.003
And I log in to a new session 17.659
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.547
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.064
Then the running Tails is installed on USB drive "to_upgrade" 19.080
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:305 2.322
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.076
Before features/support/hooks.rb:259 0.007
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.986
Then all tps features from the old Tails version are active 1.574
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.034
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.339
After features/support/hooks.rb:305 0.627
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:30.260
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.375
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.071
And Tor is ready 22.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.054
Given I shutdown Tails and wait for the computer to power off 8.602
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.695
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.595
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.314
When the network is plugged 0.039
And Tor is ready 17.341
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.458
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.732
Given I shutdown Tails and wait for the computer to power off 4.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.885
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.043
And Tor is ready 19.925
Then the Upgrader considers the system as up-to-date 0.309
# 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.779
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:305 0.813
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
34.474
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.568
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.465
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 17.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.428
After features/support/hooks.rb:305 0.972
After features/support/hooks.rb:89 0.000