Testing this feature requires a working Solr server.

1. Visit Site administration / General / Advanced features and turn on Enable global search if necessary.
2. Visit Site administration / Plugins / Search / Manage global search and select the Simple search search engine (not Solr) under Select search engine.
3. Visit the status checks page (Site administration / Reports / System status).
   • EXPECTED: There should be no 'Solr' check.
4. Visit Site administration / Advanced features and turn off Enable global search.
5. Visit Site administration / Plugins / Search / Manage global search, select the Solr search engine under Select search engine, and set Index when disabled to no (default).
6. Visit the status checks page again.
   • EXPECTED: There should still be no 'Solr' check.
7. Visit Site administration / Advanced features and turn back on Enable global search.
8. If necessary, set the Solr configuration (Site administration / Plugins / Search / Solr) so that it is correct and points to a working Solr server.
9. Visit the status checks page again.
   • EXPECTED: There is a 'Solr' check, and it shows green (OK) along with the time taken to get status (e.g. 0.02s).
10. Click the More info link next to the Solr check.
    • EXPECTED: In addition to the information shown on the front page, it also shows the size of the search index e.g. The index is using 50.1 KB on the Solr server (this could be very small for a newly-created one, or larger if there is some data).
11. Go to the Solr configuration screen (which you can now get to by clicking Settings next to the Solr check) and change the Solr settings so that it does not connect. The easiest way to do this is to change the hostname by adding some incorrect character to the start. Save changes.
12. Visit the status checks page again.
    • EXPECTED: The Solr check is now showing red (Error) with a suitable message e,g, Cannot connect to Solr server. (This may add up to 5 second delay to the pages.)
13. Click the More info link.
    • EXPECTED: In more info, it shows you the full exception for the failed connection attempt.
14. Go to the Solr configuration screen (Settings next to Solr check) and fix the settings back to correct values (correct the hostname); also, under Index size limit set a value for the index size which is very slightly higher than than the real size for the index you saw in step N. Save changes.
15. Visit the status checks page.
    • EXPECTED: The Solr check is now showing yellow (Warning) and the index size message e.g. The index is using 50.1 KB on the Solr server.
16. Go to the Solr configuration screen (Settings next to Solr check) and set Index size limit less than the real size for the index you saw in step N. Save changes.
17. Visit the status checks page.
    • EXPECTED: The Solr check is now showing red (Error) and Index larger than specified size.

Code verified against automated checks.

Checked MDL-83119 using repository: https://github.com/sammarshallou/moodle.git

• main (0 errors / 0 warnings) [branch: MDL-83119-main | CI Job]

_{More information about this report}

Built on: Mon 21 Oct 2024 08:36:24 AM UTC

Launching automatic jobs for branch MDL-83119-main

• https://ci.moodle.org/view/Testing/job/DEV.02%20-%20Developer-requested%20PHPUnit/17054/ PHPUnit (sqlsrv)
• https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/58056/ Behat (NonJS - boost and classic)
• https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/58057/ Behat (Firefox - boost)
• https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/58058/ Behat (Firefox - classic)
• https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/58059/ App tests (stable app version)

Built on: Mon Oct 21 06:25:27 AM UTC 2024