Project Number Date
test_Tails_ISO_devel 3571 31 Oct 2024, 14:57

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:36.502 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:7.327
Before features/support/hooks.rb:269 0.009
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.525
When I start Tails from USB drive "old" with network unplugged 1:29.224
Then the boot device has safe access rights 3.240
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.763
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.258
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:33.294
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 30.414
And I take note of which tps features are available 1.701
Then a Tails persistence partition exists on USB drive "old" 0.897
And I shutdown Tails and wait for the computer to power off 6.410
After features/support/hooks.rb:326 0.224
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.457
Before features/support/hooks.rb:269 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.938
Then Tails is running from USB drive "old" 0.657
And all tps features are active 2.021
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.800
And I take note of which tps features are available 0.386
And I shutdown Tails and wait for the computer to power off 4.398
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.635
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.805
Before features/support/hooks.rb:269 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 11.988
And I log in to a new session 19.354
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.869
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.047
Then the running Tails is installed on USB drive "to_upgrade" 24.662
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.116
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.200
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.542
Then all tps features from the old Tails version are active 1.876
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.525
And all persistent directories from the old Tails version have safe access rights 2.570
After features/support/hooks.rb:326 1.191
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:33.226
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 14.060
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.055
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.087
And Tor is ready 23.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.887
Given I shutdown Tails and wait for the computer to power off 13.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.225
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.277
When the network is plugged 0.071
And Tor is ready 19.148
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.785
Given I shutdown Tails and wait for the computer to power off 6.635
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.372
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.292
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.354
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.352
When the network is plugged 0.053
And Tor is ready 18.089
Then the Upgrader considers the system as up-to-date 0.294
# 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.903
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.002
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
41.225
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.505
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.917
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.755
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 22.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.203
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.000