Project Number Date
test_Tails_ISO_20522-ocr-more 37 22 Jan 2025, 05:26

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:52.823 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
1:54.881
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.811
When I start Tails from USB drive "old" with network unplugged 1:19.782
Then the boot device has safe access rights 2.960
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.784
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.955
Before features/support/hooks.rb:269 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:22.402
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.489
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.866
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.445
Then Tails is running from USB drive "old" 0.316
And all tps features are active 2.063
When I write some files expected to persist 1.999
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.418
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.065
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.958
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.953
And I log in to a new session 18.636
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.408
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.472
Then the running Tails is installed on USB drive "to_upgrade" 21.671
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.523
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.876
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:0.912
Then all tps features from the old Tails version are active 1.637
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.157
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.283
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:33.558
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 34.275
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.543
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.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.067
And Tor is ready 20.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.901
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.575
Given I shutdown Tails and wait for the computer to power off 8.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.692
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.472
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.276
When the network is plugged 0.073
And Tor is ready 17.755
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.309
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.024
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.157
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.983
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.271
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.080
And Tor is ready 19.606
Then the Upgrader considers the system as up-to-date 0.309
# 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.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.887
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.726
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.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.744
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 20.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.471
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.000