Different Testing Scenerios

COE: Enterprise Systems


1. Performance testing baseline.

2. process & methodology approach

3. Production certification sign off

4. Standards

5. testing infrastructure & environment

6. Bug fixing, optimizations and tuning

7. tools usage

8. product & applications evaluations/bench marking





Mainframe Applications:

1. Start gaining the application knowledge

2. Collect the information and documents related to the application

3. Analyzing the code and functionality of the screen

4. Create the Test Scenarios based on the screens

5. In each test scenarios to be divided into based on the business functionality

6. Based on the functionality will have test cases to be created.

7. Test cases will have the structure of Create, Edit i.e. update or modify and delete.

8. Check how many screen in that scenario

9. how many fields in one screen

a. Adding new fields

b. Editing fields

c. Verify the fields

d. Delete the fields

10. create test cases in manual testing perspective

11. create test cases in excel sheet

12. check for all types of testing

a. positive

b. negative

c. junk



1. these applications are running on legacy systems

2. understanding of business functionality and writing the test cases

3. best for regression testing

4. estimation is touch to do

5. individual application testing (ERP, CRM, SCM)

a. Product based testing

b. Mainly concentrated on the requirements

c. Need to validate only valid test conditions



Screen Based Validations:

1. count the number of screens

2. each screen validation of the fields

3. count number of fields



Requirements:

Test plan

Test lab

Test Defects



Applications:

1. Individual application (single) no interaction between any other application interface

2. two or three application interaction

3. more than five application interaction

Basically it has divided into various business areas



Example: JPMC bank one

JPMC:

1. Financial services

2. Card services

3. Stock marketing

4. Loans & insurance



Web application testing:

Stock marketing applications

1. futures & options

2. Shares

3. commodities



1. in these most of the business logic is buy/sell

2. it should be by a person

a. Customer

b. Agent

c. Client

3. ultimately either with draw or deposit is done in the bank account

Comments

Post a Comment

Popular posts from this blog

Terminal Emulation – QTP Automation Testing

Terminal Emulation – QTP Automation Testing Topics to be covered 1. Basic understanding of the terminal emulator 2. Emulation terminology 3. Configuring the QTP to work with TE application 4. Automation testing methodology Basics of Emulator • Duplicates the functions of one system using a different system, so that second system behaves like a first system. • Computer simulation Example: AS400 and mainframes is a dark green color screen AS400 is introduced in the year of 1988 by IBM, formally renamed as IBM iseries but still called as AS400 is mid range server for the small business and large enterprises. It will work good within distributed network and web based applications for execution it uses OS400 ie operating systems. TN5250 Terminal emulation protocol IBM owned iseries access by TN5250 with WRQ’s reflection, humming bird’s host explorer, Cybele software’s Z scope Express 5250. AS400 is also a Mainframe which are used for large organizations, for critical applic...
Read more

HP QC SQL Queries

Test-lab: SELECT CY_CYCLE AS "Test Set",        TS_NAME AS "Test Script Name",        TC_ACTUAL_TESTER AS "Tester",        TC_STATUS AS "Execution Status",        LEFT(CONVERT(VARCHAR,TC_EXEC_DATE,20),10)  AS "Execution Date" FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleid) Test-Summary: SELECT CY_CYCLE,        TC_STATUS,        COUNT(TS_NAME) FROM TEST, TESTCYCL, CYCLE WHERE CY_CYCLE_ID = TC_CYCLE_ID AND   TS_TEST_ID = TC_TEST_ID AND CY_CYCLE_ID IN (cycleid) GROUP BY CY_CYCLE, TC_STATUS ORDER BY CY_CYCLE, TC_STATUS Run-rate: SELECT CY_CYCLE,        TC_ACTUAL_TESTER,        TC_STATUS,        L...
Read more

Challenges while executing the test cases for large project

Defects are in Closed status but the test scripts in either Not Completed or Failed or Blocked Status. Based on the conversation with Program Director regarding this, we have followed this method to get more productivity Identify the defects which are closed and find the linked test scripts. Moved those to No Run status by updating the comment section in the test plan>>Run suite. Identified the test scripts which are in the Not completed status for more than two or three days Check the test steps status and if there is an update on those ie more than 50% of the test steps has been executed in that case need to check with the concerned tester for further update. Else move the test script to no run status. Possibility of no action on the test scripts due to concern tester is moved out of the portfolio or left the company or not feeling well or any emergency Defect is in "closed" status, so the test script is moved to "No Run" status t...
Read more