tree 5b3e8820a6cb71615db4b52672a38980f1516df1
parent 96aa415e1f9d7762dbeb2accd8da14ed2878a6eb
author Marc Kupietz <kupietz@ids-mannheim.de> 1781461554 +0200
committer Marc Kupietz <kupietz@ids-mannheim.de> 1781461869 +0200

Fix false-positive failures in "has hits" search tests

The search tests sometimes reported failure (and fired notifications) even
though the result page showed matches. Two changes:

- The per-search mocha timeout was a hard 20s, shorter than search()'s own
  internal waits, so a slow total-count computation could trip it before the
  count was read. The timeout is now configurable via KORAP_SEARCH_TIMEOUT
  (default 60s).

- search() no longer relies on a fixed 2s sleep. It waits until the result
  page has settled -- the total is shown, matches are listed, or a "no
  matches" message appears -- and reads the outcome immediately.

Note this slightly relaxes what "has hits" verifies: when glimpse/cutoff is
on, Kalamar lists matches without computing a total, so the test now accepts
the presence of listed matches as proof of hits rather than requiring a
counted total. This keeps the check stable across glimpse states; when
glimpse is off the exact total is still read and asserted.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Change-Id: I92f2004ba668722939e3a70e3ab8aa7eae698b4d