How to start Testing?
As to start testing, Tester needs test scenario & test cases because Test scenario tells ‘What to be test’ and test case tells ‘how to be test’ which includes a detailed procedure and expected behavior.
The following thing needs to write good test cases:
1. Mock up ‘Screen’& Use Cases (it includes pictorial representation of screen & workflow)
2. User Story. it includes screen, flows and functionality.
3. High Level Document: It is the overall system design covering the system architecture and database design. It describes the relation between various modules and functions of the system. data flow, flow charts and data structures are covered under HLD. Acceptance Testing is used in this design process.
High level documents are:
1. SRS 2.Test Plan 3. Test Stratergy
4. Low level document: Low Level Design is like detailing the HLD. It defines the actual logic for each and every component of the system. Class diagrams with all the methods and relation between classes comes under LLD. Programs specs are covered under LLD. Unit and Integration Testing is used in this design process.
1. Test Case Design 2. Defect Logging etc. (includes every Action)
Use case: Use Case is a pictorial representation of the business logic and work flow that includes series of steps an actor performs on a system to achieve a goal. i.e. a description of a particular use of the system by an actor or user. Use Case is written in Business Design Document (BDD) by the Business Analyst. It is for understanding the functionality for the person who is involved in writing/identifying the test cases that cover the entire system, on a transaction by transaction basis from the start to finish.
User stories: (requirement doc)
User Stories are short, simple descriptions of a feature told from the perspective of the person (client) who desires the new capability, usually a user or customer of the system. It is actually a test requirement of client. They typically follow a simple template:
As to start testing, Tester needs test scenario & test cases because Test scenario tells ‘What to be test’ and test case tells ‘how to be test’ which includes a detailed procedure and expected behavior.
The following thing needs to write good test cases:
1. Mock up ‘Screen’& Use Cases (it includes pictorial representation of screen & workflow)
2. User Story. it includes screen, flows and functionality.
3. High Level Document: It is the overall system design covering the system architecture and database design. It describes the relation between various modules and functions of the system. data flow, flow charts and data structures are covered under HLD. Acceptance Testing is used in this design process.
High level documents are:
1. SRS 2.Test Plan 3. Test Stratergy
4. Low level document: Low Level Design is like detailing the HLD. It defines the actual logic for each and every component of the system. Class diagrams with all the methods and relation between classes comes under LLD. Programs specs are covered under LLD. Unit and Integration Testing is used in this design process.
1. Test Case Design 2. Defect Logging etc. (includes every Action)
Use case: Use Case is a pictorial representation of the business logic and work flow that includes series of steps an actor performs on a system to achieve a goal. i.e. a description of a particular use of the system by an actor or user. Use Case is written in Business Design Document (BDD) by the Business Analyst. It is for understanding the functionality for the person who is involved in writing/identifying the test cases that cover the entire system, on a transaction by transaction basis from the start to finish.
User stories: (requirement doc)
User Stories are short, simple descriptions of a feature told from the perspective of the person (client) who desires the new capability, usually a user or customer of the system. It is actually a test requirement of client. They typically follow a simple template:
No comments:
Post a Comment