Project Number Date
test_Tails_ISO_stable 4826 04 May 2024, 12:09

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 18:10.867 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:0.181
Before features/support/hooks.rb:259 0.006
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.293
When I start Tails from USB drive "old" with network unplugged 1:24.851
Then the boot device has safe access rights 2.858
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:305 7.092
After features/support/hooks.rb:89 0.009
Tags: @product
2:5.397
Before features/support/hooks.rb:259 0.006
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 1:21.293
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 32.665
And I take note of which tps features are available 1.871
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:305 0.186
After features/support/hooks.rb:89 0.009
Tags: @product
2:43.700
Before features/support/hooks.rb:259 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.237
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.845
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.656
After features/support/hooks.rb:305 0.093
After features/support/hooks.rb:89 0.009
Tags: @product
2:23.096
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 10.102
And I log in to a new session 16.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.470
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.995
Then the running Tails is installed on USB drive "to_upgrade" 14.759
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:305 6.713
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.946
Before features/support/hooks.rb:259 0.006
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.498
Then all tps features from the old Tails version are active 3.078
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.209
And the expected persistent files created with the old Tails version are present in the filesystem 1.366
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:305 0.662
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:11.972
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.063
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.528
When the network is plugged 0.039
And Tor is ready 22.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.649
Given I shutdown Tails and wait for the computer to power off 8.689
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.691
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.118
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.288
When the network is plugged 0.043
And Tor is ready 16.475
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.676
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.880
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.314
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.848
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.042
And Tor is ready 20.431
Then the Upgrader considers the system as up-to-date 0.290
# 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 13.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.950
After features/support/hooks.rb:305 0.763
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
33.571
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.595
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 17.338
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.041
After features/support/hooks.rb:305 0.637
After features/support/hooks.rb:89 0.000