Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 11 29 Jul 2024, 16: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 20:17.962 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:32.390
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.705
When I start Tails from USB drive "old" with network unplugged 1:51.482
Then the boot device has safe access rights 3.854
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:326 7.274
After features/support/hooks.rb:100 0.012
Tags: @product
2:12.131
Before features/support/hooks.rb:269 0.009
Given a computer 0.585
And I start Tails from USB drive "old" with network unplugged and I login 1:27.345
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.682
And I take note of which tps features are available 1.430
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.920
After features/support/hooks.rb:326 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.036
Before features/support/hooks.rb:269 0.006
Given a computer 0.323
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.827
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.231
When I write some files expected to persist 1.977
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.819
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.443
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.837
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.569
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 10.957
And I log in to a new session 23.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.660
Then the running Tails is installed on USB drive "to_upgrade" 22.013
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.918
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.039
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.556
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.595
And the expected persistent files created with the old Tails version are present in the filesystem 2.035
And all persistent directories from the old Tails version have safe access rights 2.596
After features/support/hooks.rb:326 1.003
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:0.630
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.575
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.044
And Tor is ready 23.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.021
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.318
Given I shutdown Tails and wait for the computer to power off 8.705
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.345
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.739
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
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.376
# 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.399
When the network is plugged 0.057
And Tor is ready 19.665
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.484
Given I shutdown Tails and wait for the computer to power off 6.687
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.067
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.425
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.038
And Tor is ready 20.455
Then the Upgrader considers the system as up-to-date 0.331
# 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 15.089
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.129
After features/support/hooks.rb:326 0.872
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.163
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.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.853
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 20.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.448
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.000