General Customer test cases Sample Clauses

General Customer test cases a. Test Cases will have a list of documented input data (initial data state) b. The Customer Testing Team will establish backup and restore points in order to return to the initial data state data in Target Platform c. Customer Testers will match and compare the baseline and Target Platform test case results to ensure the translation was correct d. For online testing, the keystrokes captured during the Source Environment baseline testing will be replayed in the online Target Platform. The test transaction results that are displayed to the end-user terminal are compared to the Source Environment results, and any differences identified. Screen captures are required to perform the matching and validation on both platforms e. For batch testing, the migrated jobs are executed in the batch environment on the Target Platform. An important key to batch testing is the identification and replacement for job steps that have external interfaces. For example, batch operations that send files via FTP or Email must be adapted so that external users do not see the results of the testing until go-live and/or the final user acceptance testing is initiated. Any interim batch test results must be evaluated without disturbing Production Applications and end-users f. At the end of the online test session or test batch job, the data state of the files on the Target Platform is compared to the data state that existed on the baseline Source Environment. Any differences are identified and documented in the defect ticket for subsequent investigation g. Data validation testing will cover the matching and validation of the output files for selected program components. These program components will be identified prior to testing for each type of conversion. Output files or reports generated in test Source Environment and Target Platform environment will be used for comparison. Sequential and Generation Datasets (GDGs) if applicable) file testing will include the validation of data created/updated/deleted and generations are incrementing correctly by comparing the extracts of input and output between Source Environment files and Target Platform environment. Source databases and corresponding Target databases on the target platform will be validated. The team will run the utilities/programs to prepare the compare files as required.
View Source

Related to General Customer test cases

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Customer Focus Is dedicated to meeting the expectations and requirements of internal and external customers; gets first hand customer information and uses it for improvements in products and services; acts with customers in mind; establishes and maintains effective relationships with customers and gains their trust and respect

  • Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.