Project Number Date
test_Tails_ISO_stable 5288 24 Nov 2024, 12:51

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:30.689 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:13.760
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.404
When I start Tails from USB drive "old" with network unplugged 1:37.249
Then the boot device has safe access rights 3.562
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.291
After features/support/hooks.rb:326 7.228
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.623
Before features/support/hooks.rb:269 0.010
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:25.846
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 34.028
And I take note of which tps features are available 1.787
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.566
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.007
Tags: @product
3:17.145
Before features/support/hooks.rb:269 0.004
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.429
Then Tails is running from USB drive "old" 1.121
And all tps features are active 2.160
When I write some files expected to persist 3.344
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 3.112
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.463
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.080
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.020
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 25.181
And I log in to a new session 21.201
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.859
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.740
Then the running Tails is installed on USB drive "to_upgrade" 25.247
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.658
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.388
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.656
Then all tps features from the old Tails version are active 1.909
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.766
And the expected persistent files created with the old Tails version are present in the filesystem 1.703
And all persistent directories from the old Tails version have safe access rights 2.749
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:51.931
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 13.332
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.643
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.074
And Tor is ready 23.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.275
Given I shutdown Tails and wait for the computer to power off 18.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.642
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.449
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.332
When the network is plugged 0.090
And Tor is ready 19.023
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.871
Given I shutdown Tails and wait for the computer to power off 4.432
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.117
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.472
And the file system changes introduced in version 6.3~testoverlayfs are present 0.605
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.079
And Tor is ready 21.213
Then the Upgrader considers the system as up-to-date 0.334
# 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 16.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.319
After features/support/hooks.rb:326 0.913
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
41.819
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.696
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.110
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.918
After features/support/hooks.rb:326 1.112
After features/support/hooks.rb:100 0.000