Fundamental of Testing

Software testing is not bug finding. it is not for attacking the developers. it never depends over various techniques. it is
very graceful manner to make confidence in software by hammering hard
to program for the assessment of the program. to achieve this! testers go
for find out the bug , so that developer can fix them....

Testing has many visible aspects to perform. fundamental process of Testing can be describe as:

1. Test Planning and Control
2. Test analysis and Design
3. Test implementation and Execution
4. Evaluating exit criteria and Reporting
5. Test closure activities

Test planing:

writer: Dear Perl !when ever I say you to dig a Pit, you can not start digging immediately. what you will do for this?
Perl: I will first ask ,where i have to make a Pit? what should be size of Pit? Depending on that i will decide for the tool and other resource that make me able to dig a Pit. 

Test Planing is used  decides a ways to achieve the objective also define the objectives. it also decides what should be perform for achieving the objective.

Control is process of monitoring that we are performing right and in given time of period very well.
*control is continuous process that interact each process for their success.

Test planing  also determine the techniques , no of people involved in team their responsibilities, Testing environment and budget for testing.

Test analysis and design:

Test analysis and design phase is that where objective takes actual shape as Test cases and conditions.
Requirements and system architecture is reviewed for better aspects, than data for Testing and conditions are specified over that requirements and architecture.
Test case are prioritized and also define either specific value is not defined for Test data. two type of Test cases are define positive and negative.  positive Test  are used to Test system functionality and negative are used to Test handling of errors that can be occur in system at execution.

Test implementation and execution

Test case are actually written here by writing procedures, creating set Test data. all information to run the Test and Test environment are setup here.
manual or automation( if needed )Testing is performed.


Evaluating Exit Criteria And Reporting.

Here we check our Tests logs. logs are measured as with our Test plans , iff both are at same level than it right time for stop Testing and also Assessing if more Tests are needed or if the exit criteria specified should be changed. we produce the reports for the stake holders.

Test Closure Activities

The main task is to Check which planned deliverable have been delivered, Closing incident reports or raising change records for any that remain open documenting the acceptance of the system, Finalizing and archiving Test ware, the Test environment and the Test infrastructure for later reuse Handing over the Test-ware to the maintenance organization, Analyzing lessons learned to determine changes needed for future releases and projects and also Using the information gathered to improve Test maturity.