Project Number Date
test_Tails_ISO_devel 3538 09 Oct 2024, 12:46

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 21:26.922 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.947
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 31.702
When I start Tails from USB drive "old" with network unplugged 1:33.686
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.592
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.032
Before features/support/hooks.rb:269 0.008
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:23.920
Then Tails is running from USB drive "old" 0.873
And I create a persistent partition 34.840
And I take note of which tps features are available 1.919
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.424
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.860
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.307
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.242
When I write some files expected to persist 1.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.673
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.772
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.461
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.469
And I log in to a new session 24.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.629
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.307
Then the running Tails is installed on USB drive "to_upgrade" 22.791
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.432
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.269
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.370
Then all tps features from the old Tails version are active 1.894
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.175
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.933
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:14.642
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 14.199
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
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.401
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.071
And Tor is ready 48.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.354
Given I shutdown Tails and wait for the computer to power off 1:22.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.877
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.603
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.467
When the network is plugged 0.093
And Tor is ready 18.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.545
Given I shutdown Tails and wait for the computer to power off 6.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.990
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
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.418
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.063
And Tor is ready 21.147
Then the Upgrader considers the system as up-to-date 0.384
# 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.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.331
After features/support/hooks.rb:326 1.575
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.709
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 11.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.591
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 1.294
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.840
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.000