Você está na página 1de 3

***** Test Initiation: first stage of STLC process. In this stage, Test Strategy document will be created.

Test strategy is a business level document which informs the Managers, Developer s and testers about what kind of testing process need to be followed. Analyze scope of project, Prepare Contract, Review of Contract, Release dates,Id entify Test Requirements and risk assessment,Identify Resources and test strateg y. what the client is requiring ............make a clear picture of system........ ******* Test planning It is a second stage in STLC where the test manager describes what type of testi ng tools is allocated to a specific tester to test the module in the developed project. The test manager simply distributes the work to different tes ters based on their experience and allocate the time to complete the work. They also decide what are requirements,form the team, decides how many seniors o r juniors are needed, and finally it needs to be approved. pass/fail criteria : For each test cases, in the test planning phase expected re sults are determined..if the actual result and expected result match it is passe d state if the actual result and expected result does not match then it is failed state. .... entrance criteria: Before the testing is proceed, the conditions or requirements are determined and it needs to be fulfilled..... exit criteria: Before announcing the completion of product, the application need s to be at least 95% or 98% correct because no one can garuantee that the application is 100% correct......All the conditions needs to be fulfilled Suspension criteria: specify the criteria to be used to suspend all or a portion of the testing activ ities while Unavailability of external dependent systems during execution. When a defect is introduced that cannot allow any further testing. A specific holiday shuts down both development and testing. resumption criteria: resumption criteria specify when testing can resume after it has been suspended. When the external dependent systems become available again. When a fix is successfully implemented and the Testing Team is notified to c ontinue testing. The contract is renegotiated with the client to extend delivery. The holiday period ends. Test design: Test design techniques provide a structured way of creating test cases. Test design types: specification-based, structure-based and experience-based.

Specification-based and experience based techniques, taken together, are collectively known as black-box techniques; structure-based techniques are known as white-box techniques. test case: A test case is providing input to the application to determine if a feature of a n application is working correctly. all positive and negative scenario created to see if all the functinality are fu lfilled Level 1: In this level you will write the basic test cases from the available sp ecification and user documentation. Level 2: This is the practical stage in which writing test cases depend on actua l functional and system flow of the application. Level 3: This is the stage in which you will group some test cases and write a t est procedure. Test procedure is nothing but a group of small test cases maximum of 10. Level 4: Automation of the project. This will minimize human interaction with system and thus QA can focus on curren t updated functionalities to test rather than remaining busy with regression tes ting. high level test case: major part low level test case : positive test case: negative test case: test execution: starts after execuation the test cases possibly expected results vary from actual results retest: found defects in the project once received modified test then retesting is done to check if the reported bugs or errors has been fixed. reexecute same test cases and scenarios smoke testing : tester acceptance testing : sanity testing:testing the major functionality narrow regression test found some defects after regression testing, then retest has to be done and deve lopment team has fix bugs . now instead of regressioon testing sanity test can be done older program works with new module regression testing: defect reporting: keep track of defect status defect verification severity/priority severity: how bad is the defect

priority: how urgent the defect needs to be fixed if all the modules are testing to ensure no defects if module 1 and module 2 are working

Você também pode gostar