Project Number Date
test_Tails_ISO_devel 3486 19 Aug 2024, 19:48

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:51.673 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:24.450
Before features/support/hooks.rb:269 0.008
Given a computer 1.004
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 33.033
When I start Tails from USB drive "old" with network unplugged 1:44.962
Then the boot device has safe access rights 3.236
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 8.603
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.405
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:24.461
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 34.261
And I take note of which tps features are available 1.469
Then a Tails persistence partition exists on USB drive "old" 0.944
And I shutdown Tails and wait for the computer to power off 8.689
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.978
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.320
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.145
When I write some files expected to persist 1.891
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.887
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.485
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.562
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.219
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.837
And I log in to a new session 19.449
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.974
Then the running Tails is installed on USB drive "to_upgrade" 18.515
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.926
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.869
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.713
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.630
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:34.882
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.476
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.574
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.079
And Tor is ready 24.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.275
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.667
Given I shutdown Tails and wait for the computer to power off 8.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.541
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.554
And the file system changes introduced in version 6.2~testoverlayfs are present 0.476
And only the 6.2~testoverlayfs SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.362
When the network is plugged 0.083
And Tor is ready 17.133
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.992
Given I shutdown Tails and wait for the computer to power off 4.612
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.904
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.063
And Tor is ready 16.169
Then the Upgrader considers the system as up-to-date 0.340
# 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.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.971
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.868
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 11.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.013
But a current signing key is available on our website 0.000
When the network is plugged 0.126
And Tor is ready 21.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.815
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000