Summary: | Tests requiring Zebra should be skipped if Zebra isn't set up | ||
---|---|---|---|
Product: | Koha | Reporter: | Jared Camins-Esakov <jcamins> |
Component: | Test Suite | Assignee: | Jared Camins-Esakov <jcamins> |
Status: | CLOSED FIXED | QA Contact: | Ian Walls <koha.sekjal> |
Severity: | normal | ||
Priority: | P5 - low | CC: | paul.poulain |
Version: | 3.6 | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: |
Bug 7724: Skip Linker test if Zebra isn't set up
[PASSED QA] Bug 7724: Skip Linker test if Zebra isn't set up |
Description
Jared Camins-Esakov
2012-03-16 11:28:37 UTC
Created attachment 8221 [details] [review] Bug 7724: Skip Linker test if Zebra isn't set up One of the tests in t/db_dependent/Linker_FirstMatch.t ony works if Zebra is running and authorities have been indexed. This was causing Jenkins agitas. The test should be skipped if Zebra isn't running or authorities have not been indexed at the time the test is run. Looks like this is only a problem when a system does have authorities, but they're not indexed or Zebra isn't running. If a system has no authorities, there is no problem. Testing a case where a system does have authorities, we now have a successful tests in both cases. The warnings returned in the STDOUT are different, giving the user a hint of what's going on, but the tests do pass. Created attachment 8319 [details] [review] [PASSED QA] Bug 7724: Skip Linker test if Zebra isn't set up One of the tests in t/db_dependent/Linker_FirstMatch.t ony works if Zebra is running and authorities have been indexed. This was causing Jenkins agitas. The test should be skipped if Zebra isn't running or authorities have not been indexed at the time the test is run. Signed-off-by: Ian Walls <koha.sekjal@gmail.com> Signed Off and Passed QA in one fell swoop. patch pushed, we will see if jenkins is back to stable ! This bug will be included in the Koha 3.6.5 release. |