Project Number Date
test_Tails_ISO_stable 4948 16 Jul 2024, 12:48

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 19:5.399 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:17.908
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.729
When I start Tails from USB drive "old" with network unplugged 1:41.035
Then the boot device has safe access rights 2.910
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.768
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.672
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:27.004
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.384
And I take note of which tps features are available 1.274
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.600
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.834
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.259
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.863
When I write some files expected to persist 1.613
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.487
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.331
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.727
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.069
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 11.015
And I log in to a new session 19.619
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.312
Then the running Tails is installed on USB drive "to_upgrade" 21.769
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.192
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.635
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.008
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 2.995
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.865
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:24.925
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 12.043
And no SquashFS delta is installed 0.189
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.112
And Tor is ready 19.889
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.186
Given I shutdown Tails and wait for the computer to power off 11.069
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.113
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.329
When the network is plugged 0.041
And Tor is ready 20.051
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.193
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.188
Given I shutdown Tails and wait for the computer to power off 4.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.615
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.189
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.033
And Tor is ready 18.891
Then the Upgrader considers the system as up-to-date 0.342
# 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.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.354
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.959
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.806
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 17.383
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.736
After features/support/hooks.rb:326 1.442
After features/support/hooks.rb:100 0.000