Project Number Date
test_Tails_ISO_stable 5104 19 Sep 2024, 13:49

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:24.749 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:5.938
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.274
When I start Tails from USB drive "old" with network unplugged 1:29.153
Then the boot device has safe access rights 3.173
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.528
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.282
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:21.840
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.732
And I take note of which tps features are available 1.660
Then a Tails persistence partition exists on USB drive "old" 0.927
And I shutdown Tails and wait for the computer to power off 8.577
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.007
Tags: @product
3:2.001
Before features/support/hooks.rb:269 0.003
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.385
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.927
When I write some files expected to persist 1.831
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.339
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.018
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.327
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.808
And I log in to a new session 22.321
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.644
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.721
Then the running Tails is installed on USB drive "to_upgrade" 20.992
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 6.724
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.821
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.840
Then all tps features from the old Tails version are active 1.775
And Tails is running from USB drive "to_upgrade" 0.443
And the boot device has safe access rights 3.273
And the expected persistent files created with the old Tails version are present in the filesystem 1.860
And all persistent directories from the old Tails version have safe access rights 2.426
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:43.629
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.081
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
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.454
When the network is plugged 0.065
And Tor is ready 21.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.044
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.094
Given I shutdown Tails and wait for the computer to power off 10.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.923
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.114
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.417
# 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.278
When the network is plugged 0.072
And Tor is ready 19.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.545
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.062
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.087
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.352
When the network is plugged 0.079
And Tor is ready 16.775
Then the Upgrader considers the system as up-to-date 10.873
# 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.603
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.748
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 10.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 1.109
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 18.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.019
After features/support/hooks.rb:326 0.893
After features/support/hooks.rb:100 0.000