Project Number Date
test_Tails_ISO_stable 5032 16 Aug 2024, 12:28

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:4.683 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:57.013
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 28.272
When I start Tails from USB drive "old" with network unplugged 1:23.804
Then the boot device has safe access rights 2.792
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.545
After features/support/hooks.rb:100 0.010
Tags: @product
2:1.696
Before features/support/hooks.rb:269 0.005
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:18.419
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 32.360
And I take note of which tps features are available 1.317
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.269
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.941
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.317
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.824
When I write some files expected to persist 1.648
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.260
And I take note of which tps features are available 0.407
And I shutdown Tails and wait for the computer to power off 4.290
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.104
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.439
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.420
And I log in to a new session 16.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.797
Then the running Tails is installed on USB drive "to_upgrade" 22.307
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:326 6.762
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.283
Before features/support/hooks.rb:269 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.381
Then all tps features from the old Tails version are active 1.428
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 2.976
And the expected persistent files created with the old Tails version are present in the filesystem 1.351
And all persistent directories from the old Tails version have safe access rights 2.666
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:10.354
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.798
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.412
When the network is plugged 0.069
And Tor is ready 22.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.039
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.984
Given I shutdown Tails and wait for the computer to power off 8.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.769
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.272
When the network is plugged 0.091
And Tor is ready 18.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.086
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.370
Given I shutdown Tails and wait for the computer to power off 4.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.878
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.942
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.076
And Tor is ready 16.137
Then the Upgrader considers the system as up-to-date 0.333
# 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.952
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.976
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.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 10.063
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.058
And the signing key used by the Upgrader is outdated 1.310
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.302
After features/support/hooks.rb:326 0.615
After features/support/hooks.rb:100 0.000