Project Number Date
test_Tails_ISO_devel 3392 17 May 2024, 12:45

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 18:33.535 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:1.028
Before features/support/hooks.rb:259 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 33.453
When I start Tails from USB drive "old" with network unplugged 1:22.173
Then the boot device has safe access rights 3.062
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:305 3.520
After features/support/hooks.rb:89 0.080
Tags: @product
2:9.167
Before features/support/hooks.rb:259 0.004
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:20.385
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 37.195
And I take note of which tps features are available 1.773
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:305 0.160
After features/support/hooks.rb:89 0.009
Tags: @product
2:51.283
Before features/support/hooks.rb:259 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.574
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.058
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.782
And I take note of which tps features are available 0.967
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.537
After features/support/hooks.rb:305 0.108
After features/support/hooks.rb:89 0.009
Tags: @product
2:28.385
Before features/support/hooks.rb:259 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 11.007
And I log in to a new session 18.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.722
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.624
Then the running Tails is installed on USB drive "to_upgrade" 19.747
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:305 6.763
After features/support/hooks.rb:89 0.000
Tags: @product
2:6.872
Before features/support/hooks.rb:259 0.006
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.769
Then all tps features from the old Tails version are active 1.527
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.081
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.636
After features/support/hooks.rb:305 0.799
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:22.694
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.789
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.043
And Tor is ready 18.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.174
Given I shutdown Tails and wait for the computer to power off 8.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.022
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.008
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.237
When the network is plugged 0.035
And Tor is ready 18.380
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.079
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.803
Given I shutdown Tails and wait for the computer to power off 4.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.213
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.866
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.033
And Tor is ready 17.176
Then the Upgrader considers the system as up-to-date 0.393
# 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 15.540
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.833
After features/support/hooks.rb:305 0.830
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
34.104
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.941
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.680
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 16.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.738
After features/support/hooks.rb:305 0.725
After features/support/hooks.rb:89 0.000