Project Number Date
test_Tails_ISO_devel 3354 18 Apr 2024, 12: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 17:46.682 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
1:36.160
Before features/support/hooks.rb:259 0.016
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 20.637
When I start Tails from USB drive "old" with network unplugged 1:10.171
Then the boot device has safe access rights 3.051
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:305 3.578
After features/support/hooks.rb:89 0.012
Tags: @product
2:7.501
Before features/support/hooks.rb:259 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:19.936
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 35.565
And I take note of which tps features are available 1.753
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.904
After features/support/hooks.rb:305 0.184
After features/support/hooks.rb:89 0.014
Tags: @product
2:44.240
Before features/support/hooks.rb:259 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.266
Then Tails is running from USB drive "old" 0.438
And all tps features are active 2.702
When I write some files expected to persist 1.808
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.522
And all persistent directories from the old Tails version have safe access rights 2.933
And I take note of which tps features are available 0.533
And I shutdown Tails and wait for the computer to power off 4.541
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.056
After features/support/hooks.rb:305 0.113
After features/support/hooks.rb:89 0.011
Tags: @product
2:25.055
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.624
And I log in to a new session 17.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.460
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.848
Then the running Tails is installed on USB drive "to_upgrade" 18.068
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:305 2.220
After features/support/hooks.rb:89 0.000
Tags: @product
2:6.319
Before features/support/hooks.rb:259 0.008
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.187
Then all tps features from the old Tails version are active 1.557
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.281
After features/support/hooks.rb:305 0.966
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:11.404
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.157
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.045
And Tor is ready 23.674
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.490
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.330
Given I shutdown Tails and wait for the computer to power off 7.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.446
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.253
When the network is plugged 0.039
And Tor is ready 19.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.154
Given I shutdown Tails and wait for the computer to power off 4.476
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.192
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.048
And Tor is ready 17.772
Then the Upgrader considers the system as up-to-date 0.258
# 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.862
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:305 0.741
After features/support/hooks.rb:89 0.029
Tags: @product @automatic_upgrade
35.999
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.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 1.536
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 18.806
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.485
After features/support/hooks.rb:305 0.744
After features/support/hooks.rb:89 0.000