A colleague of mine recently asked me, “Where should I start with for preparation for an interview? It's almost 2 years I have faced any interview.”
My answer was straightforward: (This will help for fresher as well as working professionals who want to switch the current job)
What do you need to know about Software Testing?
First basic thing – Testing Concepts: One needs to be very good at this especially the Manual Testing methodologies. But only knowing different testing concepts is half work done. The next – most important thing is to know which type/technique/concept of testing can be applied at what stage of SDLC.
“What should I test and when?” is very important. There might be some concepts, which do not apply to what we, professionals test in our company, but it's always better to have an idea of all testing practices.
Many freshers and working testing professionals have might not work on various testing domains like Localization Testing, Time Zone Testing, etc.
But knowing more than what you have worked on will help you better answer the different questions from the interviewer. I always try to keep my testing knowledge updated besides my current project work. This helped me a lot while switching my job some years ago.
What if an interviewer asks you a question on the topic, which you have never worked on? For example, you don't have any experience on web-based projects or Client-Server Testing and the interviewer asks you to test the “Yahoo mail application”. Will you be able to answer this question? You can.
Even if you have not worked on this type of project. How? Your curiosity to learn the things you never have done before will help you in this case. To broaden your thinking area, be curious about every work and every query you face in your daily work routine.
Knowing more is harmless and will help you at least to give your thoughts on the questions asked by the interviewer.
If you don't know any testing concept, For example, “Localization Testing”, then try to learn the concepts first, like – what would be Localization Testing?
It’s simple: Test if the application looks local for you while using. Then go on exploring. See for used colors, content, images, culture, etc, different countries, locales have it differently.
Consider a web site that reads from right to left, is it accepted in countries other than the Middle East? Obviously NO. Or, can you display the same geo-specific content in India what you can display in the US? Again NO. This is just a simple example of how you can learn unknown testing concepts.
The very essential part of a test engineer is “Thinking out of the box”. If you are not capable of thinking out of the box, believe me, testing is not for you.
What do you mean by thinking out of the box? Don't just follow the traditional methods. Implement new things in testing. Try to summarize, automate the routine testing work. Think from a user perspective. Think about how the user will use your application.
What are the common mistakes that he can make or which tasks he can perform on your application? This way you will get an insight into any application and will also help to answer the questions in depth.
Besides from “curiosity to learn” you should upgrade your skill in the following areas:
- Some hands-on basic Database/SQL queries and concepts.
- Any basic scripting language (for Automation Testing).
- Networking and system administration concepts will help you in system domain projects.
Do not just write the UI test cases, check what is happening inside the application. For application having database connection check for data updating, retrieving and in any case there should not be loss of data.
Get hold on the project. Know the application under test before starting to test it. Instead of looking in the requirement document, look into the architecture doc, design doc, sequence diagram, and activity flow diagram.
Most importantly you need to be perfect in what you have mentioned in your CV. All the questions the interviewer asks will be based on what you are specifying in your CV. So do not mention the skills you have not worked on, just for the sake of decorating the CV with multiple skills.
The key point in the interview is, You should make the interviewer feel that it was a complex application you were testing and had a lot many challenges in it for a tester!
And one last thing – If you don't know the answer to a question, say so. Don't fool around and get into trouble.
If you have any queries on “Preparation for a Testing interview” then comment it below.
To get email notifications of new articles on Software Testing to subscribe to our email newsletter.