Project Number Date
test_Tails_ISO_devel 3619 22 Dec 2024, 12:39

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:8.674 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:5.286
Before features/support/hooks.rb:269 0.005
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.272
When I start Tails from USB drive "old" with network unplugged 1:30.824
Then the boot device has safe access rights 2.956
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 7.045
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.706
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:24.457
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 29.781
And I take note of which tps features are available 1.731
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.871
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.330
Then Tails is running from USB drive "old" 0.387
And all tps features are active 1.968
When I write some files expected to persist 2.003
# 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.357
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.400
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.123
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.591
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.825
And I log in to a new session 18.993
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.704
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.911
Then the running Tails is installed on USB drive "to_upgrade" 24.308
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.380
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.228
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.942
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.230
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.426
After features/support/hooks.rb:326 0.596
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.954
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.398
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.067
And Tor is ready 25.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.378
Given I shutdown Tails and wait for the computer to power off 10.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.119
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
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.297
# 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.269
When the network is plugged 0.068
And Tor is ready 19.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.856
Given I shutdown Tails and wait for the computer to power off 4.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.343
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.062
And Tor is ready 18.700
Then the Upgrader considers the system as up-to-date 0.404
# 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.771
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.935
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
43.035
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.802
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
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.739
But a current signing key is available on our website 0.000
When the network is plugged 0.194
And Tor is ready 25.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.918
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.000