Project Number Date
test_Tails_ISO_devel 3553 18 Oct 2024, 12:53

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:55.835 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:35.487
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.821
When I start Tails from USB drive "old" with network unplugged 1:58.010
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.726
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.448
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:33.057
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 34.544
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.794
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.013
Tags: @product
3:3.778
Before features/support/hooks.rb:269 0.010
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.046
Then Tails is running from USB drive "old" 0.686
And all tps features are active 2.188
When I write some files expected to persist 1.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.984
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.126
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.433
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.072
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 9.068
And I log in to a new session 18.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.758
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.713
Then the running Tails is installed on USB drive "to_upgrade" 23.884
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.321
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.690
Before features/support/hooks.rb:269 0.005
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.533
Then all tps features from the old Tails version are active 1.790
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.318
And the expected persistent files created with the old Tails version are present in the filesystem 1.841
And all persistent directories from the old Tails version have safe access rights 2.563
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:32.972
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 11.815
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.143
And Tor is ready 19.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.657
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.960
Given I shutdown Tails and wait for the computer to power off 10.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.150
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
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.371
# 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.407
When the network is plugged 0.079
And Tor is ready 17.918
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.551
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.104
Given I shutdown Tails and wait for the computer to power off 6.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.492
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.439
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.269
When the network is plugged 0.079
And Tor is ready 20.016
Then the Upgrader considers the system as up-to-date 0.295
# 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.221
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.008
After features/support/hooks.rb:326 0.691
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.385
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 12.385
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.880
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.416
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000