I still get numerous parsing errors when opening your project files
with BaseX, and I’m sorry I don’t have time to track all this down. If
you believe that anything of your code that can still be dropped, feel
free to give it a go. See e.g. [1] for some hints on some suggestions.

[1] https://stackoverflow.com/help/minimal-reproducible-example


On Sat, Feb 19, 2022 at 6:30 PM Eliot Kimber
<[email protected]> wrote:
>
> Let me remake the sample code—it should all be there—with my now-working job 
> construction log.
>
>
>
> The issue with the unit tests not seeing the results of the jobs remains.
>
>
>
> I’ve attached take 2 of the code, which fixes my earlier bug with job 
> creation and running, so that, for example, the test:runMultipleJobs test 
> does create all three expected databases, meaning the chain of three jobs ran.
>
>
>
> I tested this code package by deleting the now/ directory from basex/repo, 
> verifying nothing works, copied the now/ directory from the zip to 
> basex/repo, ran the test from the zip in the GUI:
>
>
>
> test /Users/eliot.kimber/temp/basex-job-test-test/test/test-orchestration.xqm
>
>
>
> which produces for me this result:
>
> <testsuites time="PT0.429S">
>
>   <testsuite 
> name="file:///Users/eliot.kimber/temp/basex-job-test-test/test/test-orchestration.xqm"
>  time="PT0.429S" tests="8" failures="4" errors="0" skipped="0">
>
>     <testcase name="createJob" time="PT0.036S"/>
>
>     <testcase name="createBadJob" time="PT0.016S"/>
>
>     <testcase name="runJobs1" time="PT0.065S">
>
>       <failure line="97" column="16">
>
>         <info>Expected database test_01 to exist</info>
>
>       </failure>
>
>     </testcase>
>
>     <testcase name="runJobs2" time="PT0.061S">
>
>       <failure line="123" column="14">
>
>         <info>Expected database test_01 to not exist</info>
>
>       </failure>
>
>     </testcase>
>
>     <testcase name="runMultipleJobs" time="PT0.041S">
>
>       <failure line="143" column="16">
>
>         <info>Expected database db1 to exist</info>
>
>       </failure>
>
>     </testcase>
>
>     <testcase name="runSwapJobs" time="PT0.074S">
>
>       <failure line="185" column="16">
>
>         <info>Expected to find doc2 in database test_swapped_to</info>
>
>       </failure>
>
>     </testcase>
>
>     <testcase name="makeJobsFromModules" time="PT0.016S"/>
>
>     <testcase name="makeSwapJobs" time="PT0.016S"/>
>
>   </testsuite>
>
> </testsuites>
>
>
>
> Cheers,
>
>
>
> E.
>
> _____________________________________________
>
> Eliot Kimber
>
> Sr Staff Content Engineer
>
> O: 512 554 9368
>
> M: 512 554 9368
>
> servicenow.com
>
> LinkedIn | Twitter | YouTube | Facebook
>
>
>
> From: Christian Grün <[email protected]>
> Date: Saturday, February 19, 2022 at 11:02 AM
> To: Eliot Kimber <[email protected]>
> Cc: [email protected] <[email protected]>
> Subject: Re: [basex-talk] Using %unit:after to verify database creation
>
> [External Email]
>
>
> I guess the function dutils:getDirectReferences is still missing in
> your example.
>
> But I’m glad to hear you’ve already found the bug.

Reply via email to