You must first learn to plan a test.
You must gain SME(Subject Matter Expert) level knowledge. To do that you should be asking hell lot of questions about domain and about software and user stories.
One of the parts is test estimation.
Here is the list of questions I usually ask.
-
What is the project? I get description of a story line.
-
Why do we require it?
-
What's my target audience?
-
List/type of users expected to work on an application.
-
Roles each user will play on a module/ project.
-
How our application will help targeted user/audience.
-
What kind of environment is expected?
-
List of modules project contain.
-
Purpose of each project
-
How inter module communication/interaction happens?
-
Data flow and impact or modifications each module have.
-
Any default functionality of an environment client is going to use. If it can be excluded from validations.
-
What are the âquality criteriaâ of the project?
-
Installation guide in case module/project requires installation.
-
How will the change request management be handled? Will it be documented?
-
Risk associated with module/project and handeling of the same.
-
Role of each tester in project.
-
Expectations from testers
-
What are the necessary resources (hardware, software and documents required to administer and execute testing â Eg., Timer Job in Sharepoint) and the status for its availability?
-
Test Documentation and execution will be done depending on the time availability and priority of the project/module (Priority for project/module should be decided by project owner (not client))