Project Number Date
test_Tails_ISO_stable 5146 06 Oct 2024, 08:34

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 20:28.213 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:11.055
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.287
When I start Tails from USB drive "old" with network unplugged 1:34.314
Then the boot device has safe access rights 3.123
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.020
Tags: @product
2:9.843
Before features/support/hooks.rb:269 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:26.597
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 31.626
And I take note of which tps features are available 1.707
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 8.361
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.012
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.998
Then Tails is running from USB drive "old" 0.481
And all tps features are active 1.996
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.689
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.465
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.964
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.333
And I log in to a new session 22.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.610
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.216
Then the running Tails is installed on USB drive "to_upgrade" 20.600
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.315
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.585
Before features/support/hooks.rb:269 0.008
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.861
Then all tps features from the old Tails version are active 1.588
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.283
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.696
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:35.895
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.506
And no SquashFS delta is installed 0.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.489
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.508
When the network is plugged 0.067
And Tor is ready 26.575
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.916
Given I shutdown Tails and wait for the computer to power off 10.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.259
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.676
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.073
And Tor is ready 47.513
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.701
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.964
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.210
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.083
And Tor is ready 47.563
Then the Upgrader considers the system as up-to-date 0.319
# 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.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.453
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
39.855
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.498
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.589
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 22.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.711
After features/support/hooks.rb:326 1.397
After features/support/hooks.rb:100 0.000