Project Number Date
test_Tails_ISO_devel 3465 16 Jul 2024, 12:54

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 20:5.357 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:31.360
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.150
When I start Tails from USB drive "old" with network unplugged 1:54.978
Then the boot device has safe access rights 3.878
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.528
After features/support/hooks.rb:100 0.035
Tags: @product
2:18.568
Before features/support/hooks.rb:269 0.008
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:34.672
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 32.035
And I take note of which tps features are available 1.638
Then a Tails persistence partition exists on USB drive "old" 0.986
And I shutdown Tails and wait for the computer to power off 8.640
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.387
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.837
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.152
When I write some files expected to persist 2.077
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.409
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.517
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.650
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.565
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 9.529
And I log in to a new session 18.542
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.150
Then the running Tails is installed on USB drive "to_upgrade" 19.931
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.216
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.592
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.954
Then all tps features from the old Tails version are active 1.742
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.711
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:3.852
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.273
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.038
And Tor is ready 20.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.695
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.047
Given I shutdown Tails and wait for the computer to power off 13.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.564
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.415
When the network is plugged 0.048
And Tor is ready 46.158
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.640
Given I shutdown Tails and wait for the computer to power off 4.260
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.473
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.770
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.059
And Tor is ready 18.651
Then the Upgrader considers the system as up-to-date 0.354
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.175
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.083
Tags: @product @automatic_upgrade
37.030
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 9.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.832
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 20.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.790
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000