So where to start testing? First you need to get all the documentation that will allow you to properly plan for testing and develop Test Cases. To do this you will need: specification, technical design, etc. Based on their pre-prepared test plan specifying the classes of tests and dates, the need for additional software, tools and equipment. This plan is discussed, adjustments are made on the basis of which the final test plan. It is important that even before the development was defined vocabulary that would enable team members to communicate in a "common language".
It should be noted that for successful work is desirable that the tester included in the development process still in the early stages, is actively engaged in discussions of the upcoming project. This will provide not only understanding of the problem, but will make the tester develops software for the same "as their child," as well as for the programmer. It is also necessary that the process of formulating a plan when you specify the timing of the testing was taken into account the time to learn the necessary documentation, including that which is necessary for theoretical training on the issue, writing the documentation necessary for testing, compiling Test Cases; study required additional software and tools for testing, installing and configuring software, hardware changes (acquisition of new and replacement of old equipment), etc. .
Following the approval of the test plan can begin to develop Test Cases, in each of the classes conducted tests. At the end of their preparation and approval, equipment replacement, learning the necessary software and documentation can begin testing. Typically, the developer will be enough time to prepare for the first time that an alpha version (or module) to send for testing.
Then begins the daily routine work the tester. Behavior Test Case, fixation of the results, a description of bugs, maintenance base, adjustment plans, etc.
Unfortunately, real life is not so smooth. Often there are situations in which seemingly has "caught" the bug when re-run the same Test Case does not occur. Moreover, a bug that you have there is a stable, may be entirely absent from the developer. Remember that before you make a bug in the framework should clearly identify the conditions under which it appears stable.
In summary you can suggest the following tentative plan for the organization of the tester from the beginning of development (general):