Project Number Date
test_Tails_ISO_stable 5282 21 Nov 2024, 12:36

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:38.375 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:18.649
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.514
When I start Tails from USB drive "old" with network unplugged 1:39.609
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 7.175
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.858
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:24.587
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 32.909
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.365
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.338
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.600
Then Tails is running from USB drive "old" 0.402
And all tps features are active 1.854
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.324
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.740
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 11.534
And I log in to a new session 19.721
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.774
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.639
Then the running Tails is installed on USB drive "to_upgrade" 22.983
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.454
After features/support/hooks.rb:326 2.156
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.038
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.996
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.593
And the expected persistent files created with the old Tails version are present in the filesystem 1.589
And all persistent directories from the old Tails version have safe access rights 2.662
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
6:35.729
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 14.087
And no SquashFS delta is installed 0.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.260
And Tor is ready 23.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.978
Given I shutdown Tails and wait for the computer to power off 10.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.746
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.374
# 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.284
When the network is plugged 0.063
And Tor is ready 20.374
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.259
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.559
Given I shutdown Tails and wait for the computer to power off 4.432
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.894
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.134
And Tor is ready 18.051
Then the Upgrader considers the system as up-to-date 0.329
# 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.666
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.895
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.022
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.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.436
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.891
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.704
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.614
After features/support/hooks.rb:326 1.017
After features/support/hooks.rb:100 0.000