Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 19 06 Aug 2024, 19:14

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:2.086 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:8.102
Before features/support/hooks.rb:269 0.006
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.123
When I start Tails from USB drive "old" with network unplugged 1:31.599
Then the boot device has safe access rights 3.095
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 4.200
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.226
Before features/support/hooks.rb:269 0.005
Given a computer 1.198
And I start Tails from USB drive "old" with network unplugged and I login 1:30.134
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 33.209
And I take note of which tps features are available 1.971
Then a Tails persistence partition exists on USB drive "old" 0.884
And I shutdown Tails and wait for the computer to power off 8.449
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.668
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.119
Then Tails is running from USB drive "old" 0.647
And all tps features are active 2.007
When I write some files expected to persist 1.602
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.697
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.125
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.211
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.331
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.847
And I log in to a new session 19.418
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.537
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.102
Then the running Tails is installed on USB drive "to_upgrade" 22.581
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.778
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.145
Before features/support/hooks.rb:269 0.004
Given a computer 0.305
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.521
Then all tps features from the old Tails version are active 2.714
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.458
And all persistent directories from the old Tails version have safe access rights 2.588
After features/support/hooks.rb:326 1.097
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:22.997
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.116
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.033
And Tor is ready 20.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.045
Given I shutdown Tails and wait for the computer to power off 8.734
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.982
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.295
When the network is plugged 0.071
And Tor is ready 20.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.516
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.934
Given I shutdown Tails and wait for the computer to power off 4.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.418
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.921
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.034
And Tor is ready 21.585
Then the Upgrader considers the system as up-to-date 0.352
# 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.689
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.054
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
31.614
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 9.637
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.790
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 14.334
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.390
After features/support/hooks.rb:326 1.173
After features/support/hooks.rb:100 0.000