Project Number Date
test_Tails_ISO_stable 5030 14 Aug 2024, 15:23

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:45.084 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:10.020
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.384
When I start Tails from USB drive "old" with network unplugged 1:32.045
Then the boot device has safe access rights 3.290
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 9.028
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.317
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:21.446
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.560
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.403
Before features/support/hooks.rb:269 0.007
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.323
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.503
When I write some files expected to persist 1.867
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 0.394
And I shutdown Tails and wait for the computer to power off 4.283
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.467
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.277
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.306
And I log in to a new session 19.168
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.886
And I plug USB drive "to_upgrade" 2.339
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.786
Then the running Tails is installed on USB drive "to_upgrade" 22.355
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.187
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.477
Before features/support/hooks.rb:269 0.007
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.034
Then all tps features from the old Tails version are active 1.581
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.259
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:15.560
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.292
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.546
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.087
And Tor is ready 18.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.930
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.015
Given I shutdown Tails and wait for the computer to power off 11.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.478
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.270
When the network is plugged 0.063
And Tor is ready 19.893
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.239
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.465
Given I shutdown Tails and wait for the computer to power off 4.106
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.167
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.962
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.063
And Tor is ready 16.638
Then the Upgrader considers the system as up-to-date 0.352
# 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.584
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.226
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.028
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 1.011
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.622
After features/support/hooks.rb:326 1.053
After features/support/hooks.rb:100 0.000