I might suggest investing in a few reference books about the fundamentals of testing before embarking on a test career. I know a lot of recruiters (and developers, and project managers, and business analysts) labor under the impression anyone with opposable thumbs can be an effective tester, but it really is a specialized skillset and knowledge base requiring some study and apptitude.
A question like "what types of software testing are there" tells me you haven't done even a cursory skim of the materials.
This is the second or third time you have hijacked an existing thread - this is against the forum rules. To familiarize yourself with the guidelines and rules we follow please read the FAQS sent to you when you registered and the following thread.
We also prefer that you do not write in "txting" but use normal language for your questions, we understand that English may be your second or third language but txting is difficult for members to read.
If you do not know much about testing you might want to learn that before moving into more advanced topics about when to automate.
The following forum provides some knowledge on testing
You don't pay attention then eventually the posts just get deleted. As a moderator it is my job to keep things clean and as a forum member it is my job to abide by rules of the forum. We all slip at times but communication is the correct way to go - as a QA Manager you should know that
[ QUOTE ]
Manually test until you can no longer test. Then automate. If you have the time to think about automation then you are ready as long as the manual tests are all completed.
[/ QUOTE ]
At the risk of hijacking a thread, there are some forms of testing that simply are too costly to perform manually and so shouldn't even be attempted. I'm specifcally thinking of load, stress, or stability testing.
I would also hope that by the time the code base was handed off to test, you wouldn't need to manually validate object or data layers and could instead start authoring automated test cases around boundary conditions and error handling.