Hello All, I am writing a test suite which involves document insertion, multiple updates to that document and deletion of that document (in that sequence). So far, in order to automate the test sequence, I got it working by coding all operations in different eval statements to different transactions and each update be visible to next step in the sequence. For orchestration, I have a URL for these tests and I can hit the url to eval test-suite code; which in turn evals all operations as different transactions. As a result, I will have my code (# of lines) grow linearly as more tests are added. I am curious if there is a better way I can keep my code more manageable and reuse it for different tests.
Thanks in advance, Ankur NOTICE OF CONFIDENTIALITY: This electronic message, including attachments, is for the sole use of the named recipient and may contain confidential or privileged information protected by State of Tennessee and Federal regulations. Any unauthorized review, use, disclosure, copying or distribution is strictly prohibited. If you are not the intended recipient or have received this communication in error please contact the sender or email i...@icainformatics.com and destroy all copies of the original message. Thank you. _______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
