Test Cases Sample Clauses
Test Cases. Supplier will provide Buyer with available test cases upon Buyer’s request.
Test Cases. For certain Problems, XxxXX may require that Customer provide XxxXX a test case and sufficient documentation to allow duplication of the Problem and the provision of Support Services. If such test case and documentation are not provided, XxxXX will be relieved of the obligation to provide any Support Services that are dependent on such test case or documentation until Customer provides such test case or documentation.
Test Cases. After the training database ---------- requirements outlined in Section 2.8.1 are met, GEMS shall accrue a test database. Such cases shall be used by R2 solely to evaluate the R2 Product algorithm. The R2 Product algorithm shall be evaluated with R2 tools. Representatives of GEMS shall participate in running the algorithm tests at R2's offices and GEMS shall have the right to access and to receive copies of all results and analyses of such tests, only for purposes related to this Agreement. R2 represents, warrants and covenants that the test cases shall not be used by R2 for any purpose other than such testing prior to the testing and analysis of the algorithm as discussed above in this Section 2.8.
Test Cases. IBM will deliver to Vision those WAS-AE test cases which are relevant to the development effort.
Test Cases. Vision will deliver to IBM those BLS and Developer Studio test suites, its BLS/WAS-AE port of those test suites, and its BLS/WAS-AE test cases that are relevant to the development effort.
Test Cases. BST uses test cases to verify that CLECs can submit pre-order and firm order transactions and send acknowledgments for these products and services via RoboTAG.
Test Cases. For paragraphs 11.5.1 and 11.5.2 above, it is tested with * and * . These tests will be completed in accordance with the mutually developed test plan. The acceptance test plan is comprised of the following cases: *
Test Cases. We will express the test cases using a syntax and vocabulary as close as possible to the one used in the DOORS functional requirements database. The intention is to produce a set of generic test cases in which each test sequence will be applicable to any particular track layout, that will stimulate the model. For instance, the various stimuli must be as close as possible to the already existing commands. The outcome of the test case will be captured from any already available statuses, signals, movements etc. In other terms, the information contained in the Command and Statuses module will be utilised. The configuration in which the system will be stimulated will be synthesised from the requirements da- tabase, where a variation on the conditions to be satisfied will be introduced for each eligible functionality. Sometimes, inexplicit conditions may be needed prior to run the test case; this will be taken in account by means of a “pre-condition” that will sit in a column by itself. These various considerations led to a structure made of eight columns (seven for the test case plus one for the countries to which the test case is applicable):
Test Cases. Test cases is a general term that includes routines/scenarios that need to be conducted to validate solution readiness. Best practices have customers creating test cases. Customers understand the workflows, data requirements, customer needs and variances from standard procedures. These items and other intrinsic knowledge result in test cases that can thoroughly prove the production readiness of the solution. It is understood that customers may have limited resources for creating test cases. Accela is willing to assist in the creation of test cases under the following conditions: Accela will assist in the creation of the Health District’s test cases based on the following expectations.
1. Accela will develop up to fifty‐one (51) test cases. The scope of each will be limited to a single business process/workflow.
2. During gap analysis, the Health District will work with Accela to identify the list of test scenarios based on the Health District’s solution groupings and workflows. The Health District will approve the final list of scenarios prior to Accela’s test case creation.
3. Prior to test case creation, the Health District will review and agree to the test case format and acknowledge the depth of testing. Test cases will follow Accela best practices. The Health District acknowledges that not all possible combinations of the data, configuration and workflow will be included.
4. Accela will submit the draft test cases for Health District review. The Health District has five
