RTM (Requirment Tracebility Matrix): means mapping between requirements and testcases to check whether all testcases are covered or not
TRM (Test Responsibility Matrix): meanswhich type oftesting technique has to be chosen to corresponding usecase
Thursday, September 20, 2007
Saturday, September 8, 2007
Difference between use case and test case
USE CASE:is a functional and system requirement of how a user uses the system being designed to perform a task.it provdes a powerful communication between customer,developer and tester...
TEST CASE:test cases r written on the basis of use case documents..that describes an input action or event and expected response to determine if a feature of an application is working correctly
TEST CASE:test cases r written on the basis of use case documents..that describes an input action or event and expected response to determine if a feature of an application is working correctly
Saturday, September 1, 2007
Relationship between SDLC or STLC
Stage 1: When Contract is signed or Organization got a project from the customer, by refering to SOW(Statement of Work) or Requirements the "UAT(User Acceptance Test) Plan is preparedand the same under goes reviews(Verification).
Stage 2. (Requirement Gathering):- Once requirement gathering or study is over the "SRS(Software Requirement Specification)" is prepared and it's reviewed(Verfication) and once SRS is finalised STP(Software Test Plan) is prepared and the same under goes reviews(Verification).
Stage 3. (High Level Design):- Taking SRS as input, HLDD (High Level Design Document) is prepared and same under goes Reviews(Verification) . Once HLDD is ready, refering the same ITP(Integration Test Plan) is prepared and the same under goes reviews(Verification).
Stage 4. (Low Level Design) :- Taking HLDD as input LLDD(Low level Design Document) is preparedand same under goes Reviews(Verification) .Once HLDD is ready, refering the same UTP(Unit Test Plan) is prepared and the same under goes reviews(Verification).
Stage 5. Coding(Impelementation):- Taking LLDD (Low level Design Document) coding will done and coding also under goes reviews(Verification).
This is all about Verification Part , Now on wards the Validation or Actual Testing starts
Stage 6. Unit Test :-Once coding of unit(s) is done , unit testing(Validation)w will be carried out by refering to the test cases (present in UTP).
Stage 7. Integration Test :- once all the units get tested, Integration testing (Validation)will be carried by refering to test cases (present in ITP).
CONTINUED ------------->
Stage 2. (Requirement Gathering):- Once requirement gathering or study is over the "SRS(Software Requirement Specification)" is prepared and it's reviewed(Verfication) and once SRS is finalised STP(Software Test Plan) is prepared and the same under goes reviews(Verification).
Stage 3. (High Level Design):- Taking SRS as input, HLDD (High Level Design Document) is prepared and same under goes Reviews(Verification) . Once HLDD is ready, refering the same ITP(Integration Test Plan) is prepared and the same under goes reviews(Verification).
Stage 4. (Low Level Design) :- Taking HLDD as input LLDD(Low level Design Document) is preparedand same under goes Reviews(Verification) .Once HLDD is ready, refering the same UTP(Unit Test Plan) is prepared and the same under goes reviews(Verification).
Stage 5. Coding(Impelementation):- Taking LLDD (Low level Design Document) coding will done and coding also under goes reviews(Verification).
This is all about Verification Part , Now on wards the Validation or Actual Testing starts
Stage 6. Unit Test :-Once coding of unit(s) is done , unit testing(Validation)w will be carried out by refering to the test cases (present in UTP).
Stage 7. Integration Test :- once all the units get tested, Integration testing (Validation)will be carried by refering to test cases (present in ITP).
CONTINUED ------------->
Subscribe to:
Posts (Atom)