I have the client requirements, initially I write test cases because some people want the record of which use cases I have tested so far, which where the documentation is useful. This is something my senior told me about writing test cases and executing test cases. Actually, I don't like writing test cases because I waste time in writing the tests.
What should I do first? I want to go through a step by step process. My goal is finding bugs in the software our developers are writing. I don't see how writing test cases will help. May I write automation script initially?
I have read in blogs that I do not need to write test cases, I need to test. The blogs say that preparing test cases is optional and that I can find plenty of bugs without preparing test cases.
Others told me that if I know about the features then I must be ready with test cases for all the use cases.
I am a beginner in testing. I want to go through the right path as I learn. Is there an accepted step by step process for a new tester to learn how to be a good tester, and if there is, what is it?