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. 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. 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.5. If the results of the testing reflect that the R2 Product is not meeting the Specifications, (a) then the R2 Product shall not be released, unless otherwise agreed to in writing by GEMS, and (b) GEMS and R2 shall share equally the test database in two halves: (i) one half of the cases shall be added to the training database and (ii) the other one-half of the cases shall remain in the test database. Any remaining test cases (from subsection (ii) above) shall not be used for testing until the next planned algorithm evaluation and shall be subject to the conditions of this Section 2.8.5.
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 TAG. • BellSouth’s LCSC staff will provide the actual test case data to CLECs prior to testing. • CLEC may be required to use their own data to test certain activities. • CLEC will provide actual data & accounts for SRT. (INSERT TEST CASES FOR CLEC USE) Appendix A - Contacts: Appendix A lists BellSouth testing and Account Team contacts: Contact Type Name Phone Number FAX BellSouth Account Representative TAG Test Manager (Non-LNP) TAG Test Manager (LNP) SAIC Process Manager Appendix B - CLEC/BST Specific Details / Sign Off: Types of Testing: Connectivity: Start Date: End Date: LAN to LAN Internet Application: Start Date: End Date: Validity: LNP Start Date: End Date: Validity: Non-LNP Start Date: End Date: SRT Test Cases Types: Pre-order Firm Order Both Description of the Types of Cases: Defined in Application Testing Plan Testing Procedures: General Agreements: Contact Type Name Phone FAX BST Account Representative CLEC Lead Negotiator CLEC Test Manager BST Test Manager (LNP) BST Test Manager (Non- LNP) SAIC Process Manager Addendum: Signed: Name BellSouth LNP TAG Test Manager Date: Name BellSouth Non-LNP TAG Test Manager Date: Name CLEC Project Manager Date: Name SAIC TAG Process Manager Date: Name BellSouth Account Team Representative
Test Cases. (split-number (join-numbers ’(3 20 39 48) 100) 100) ;-> (3 20 39 48)
Test Cases. (chars->bytes (string->list "hello")) ; -> (104 101 108 108 111) ;;;(chars->bytes (string->list "\u0000\u0000\u0000")) ; -> (0 0 0) ;;;(chars->bytes (string->list "\u3293\u5953\uabab")) ;;; -> (255 147 50 255 83 89 255 171 171) (define bytes->chars ;; Inverse of chars->bytes. Takes a list of integers that encodes a ;; sequence of characters, and returns the corresponding list of ;; characters. Integers less than 255 are converted directly to the ;; corresponding ASCII character, and sequences of 255 <low-byte> ;; <high-byte> are converted to a 16-bit Unicode character. (lambda (bytes) (if (null? bytes) ’() (let ((b (car bytes))) (if (< b 255) (cons (integer->char b) (bytes->chars (cdr bytes))) (let ((lowbyte (cadr bytes)) (highbyte (caddr bytes)))
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):
