You have two advantages here,
1) Being new to the project
You will test the product as if you are a customer using the product for the first time.
If being a user with zero knowledge about the product forces you to ask so many questions and dig through documentation to do even the simplest tasks. Then there is a serious problem with the UX design.
you can write down all the user experience issues you have faced during this phase, which could include:
- Need for tooltips
- Proper color coding and error message to show user mistakes
- Need for more visually appealing design
- And so on
Don't hesitate to write down even the simplest observations. Eg: renaming back button as an edit button, providing direct links to some page. and so on.
In short, write down whatever that comes up during your Exploratory testing phase
2) Having little experience:
Even though you have very little experience, the organization has realized your potential and has given you a great opportunity. If an organization has trusted you with such responsibility, then it shows how talented you are.
So it's just the matter of tieing your shoes and believing in your self. Go there and show how to "Break the unbreakable"
The advantages you have here is :
- You will have more time to learn stuff
- No one expects you to be a test architect
- You can fail, and can still look smart when you figure out why that approach failed
- You can have something great to put in your CV
- You can be proud that you are going to set a quality process for that team.
Now on how to start testing:
As explained, try to understand a high-level idea of the "Software
under test" and start "Exploratory testing". Write down all
Try to understand the backend service. If they are using APIS, then
see how API contract works ( contract is just a document that says
when you send 'A' to the API (www/google/map) you get 'B')
Now once you have done exploratory testing, and understood how API
works. start automating APIs
Then start with UI automation
Automation is really simple, its about asking questions. It's about automating things you already do manually.
1) API automation:
Question: how to validate that all API response fields are correct?
Ans: schema validation
Question: how to validate that request was successful?
Ans: response code should be 2xx
and so on.
so decide a tool, eg: postman, and google on how to validate status code is 200. Then reuse the same logic for all other status codes
- UI automation:
UI automation has nothing to do with how the application looks. We are testing that the UI element's functionality is working fine.
eg: you click a button and then something should happen. So in automation, you choose a tool and then google how to click a button, then you google how to validate that the expected thing happened.
In UI automation, the main thing to learn is Page object model
- Decide a tool
- Start using it
- It fails
- Ask why it failed
- You learn something, and now implement it