How do I start with testing . .?. .

Think twice (or may be more) times before you choose a career. Are you interested in it or do u just want to jump on the bandwagon?

Prerequisite 

You can join a software development company as a tester if you can convince the interviewer 

1. You have a knack for breaking software

2. You are aware of basic Quality concepts and be live in them

3. You want to pursue Testing as a career and not just to try it 

OO Software Testing Issues 

A common way of testing OO software testing-by-poking-around (Binder, 1995). In this case the developer’s goal is to show that the product can do something useful without crashing. Attempts are made to “break” the product. If and when it breaks, the errors are fixed and the product is then deemed “tested”. 

Testing-by-poking-around method of testing OO software is, in my opinion, as unsuccessful as random testing of procedural code or design. It leaves the finding of errors up to a chance. 

Another common problem in OO testing is the idea that since a super class has been tested; any subclasses inheriting from it don’t need to be.

This is not true because by defining a subclass we define a new context for the inherited attributes. Because of interaction between objects, we have to design test cases to test each new context and re-test the super class as well to ensure proper working order of those objects. 

Yet another misconception in OO is that if you do proper analysis and design (using the class interface or specification), you don’t need to test or you can just perform black-box testing only. 

However, function tests only try the “normal” paths or states of the class. In order to test the other paths or states, we need code instrumentation. Also it is often difficult to exercise exception and error handling without examination of the source code.