For new graduates or even students still sitting in the school chair, the interview is no longer a strange term. Before the interviews, I carefully prepare the knowledge related to my specialty to interview, but many of you will ask the question, what questions will the employer ask? Today I will share with you the frequently asked questions in QA / Tester interviews for newly graduated students or beginners.
I. Frequently asked questions
1. Please introduce yourself
This is the question that almost opens every interview. Introduce yourself, what information should you introduce?
- What is your name? Are you still a student or graduate now? Which school, what school?
- What are short term goals? What are long-term goals?
- What are the strengths and weaknesses?
The employer will ask you more about your career goals: for example, do you have any specific plans for your goals?
2. Why did you choose QA? How long have you been studying this QA job?
- I really like learning about information technology, after learning I really love the work of QA / Tester. QA / Tester is an important position in the software development process, ensuring the best finished product before reaching the end users.
- Time you learned: For example, where did you go to school at some time? Or studying at school ……..
3. During the writing of test case, which techniques do you usually use?
If you apply to the manual test position, list the techniques in black box testing such as: equivalent partitioning technique, boundary value analysis technique, decision table technique, state transition technique, using use case, .. You need to identify and explain these techniques if you are hard to explain then you can get specific examples.
In this verse is usually done when you answer the interviewer will often ask you questions: Distinguish technical equivalence partitioning and technical analysis of boundary value
4. What are the common components in a test case?
Depending on the template of each company, however, in a test case, there will usually be the following components:
- ID : the number of the test case
- Function / Screen: Function or screen to be tested
- Test case name: Brief description of the case to be tested
- Prerequisite: The condition needed before executing that case
- Steps to perform: Describe in detail the steps to test that case
- Desired results: Results of the case that the customer wants
- Results: The outcome of the case when performing the test eg passed, failed, peding, N / A, … depending on the company.
- Date of test: The date the tester / QA performed the test
- Tester: The name of the Tester / QA that performs the test case
- Note: Note down what should note that the case for example when the test result is fail, then we need to record links you’ve logged onto the ticket that makes tracking easy
After answering, the recruiter will ask you how to write an effective test case?
5. Which cases will I test for the case of entering a natural number between 0-100?
I will incorporate techniques of analyzing boundary values and equivalent partitions to test cases as follows:
- Empty
- Enter the entire space
- Enter 0
- Enter -1
- Enter 50
- Enter 100
- Enter 101
- Enter the decimal number
- Enter the fraction
- Enter the word
- Enter the special characters: [email protected] # $% ^ & * ()
- Enter the html tag: <table> Test </table>
- Enter sql injection: ‘a’ or ‘1 = 1–‘
6. When do I log the bugs and the components that are in a bug report?
When I ran the test and found that the actual result was different from the expected result, I had to log a bug.
Depending on the company or each bug management tool, there will be different components. I would like to present about the common components when using redmine tool to manage errors:
- Title: This section will give a brief description of how the bug looks and can immediately understand where the error is happening. Should be written according to the structure:
[Prefix] How to display errors + When users do anything on any screen
For example: [User] [Apply job] Do NOT display error message when user input invalid value into “Email” field - Description: A bug description, usually composed of the following components:
- Sumary : Summarizing the bug, if the title has not clarified the bug, under the sumary section will add and clarify the bug, so stop at 3 sentences.
- Pre-condition: Before this bug, there must be something before. Depending on each bug, there is Pre-condition.
For example: If you want to edit a resignation form, a form must have been successfully created before - Step to re- produce: The steps to reproduce the bug are the same as the steps in the test case
- Expected result: Expected result of a bug
For example: Sign up successful account - Actual result: Actual result of the bug (how the system is actually running)
- Note: Record the test environment of the bug, Requirement says and specify which part of the page how much then paste the link
Attachment: Attach an image or gif to reproduce the bug
There are also components:
- Priority: Priority of the bug
- Severity: The severity of the bug
7. Based on where to determine the expected results
The expected expected outcome is based on:
- Requirement
- Q&A file
- Tickets on the management tool (such as redmine)
8. When writing test cases, how often do you test cases?
When writing test cases I often test cases as follows:
- Check GUI (genaral user interface): Check the interface
- Check screen flow: Check the screen flow
- Check permission role: Check to see which roles access that screen
- Check initial display: Check the initial display of the fields in the screen
- Ckeck Function: Go into details of each function and each field 1.
II. Some tips when interviewing
1. How to prepare for the interview
- There will be people who are preparing for an interview tomorrow to review the knowledge tonight, and some people have done it before 1 day, 2 days, 3 days or 1 week. However, the accumulation of knowledge is a long process, the knowledge is accumulated day by day rather than day 1 and you can cram them all in the head. That’s why every day I should cultivate my knowledge. Only mastering my own knowledge can confidently answer questions and only practice daily to be better.
- If you are not confident or trembling, ask yourself questions daily and answer them out loud or practice in front of the mirror.
- Before going to the interview, you should update your CV 1 carefully to avoid the case of one CV sent to dozens of companies.
In addition to preparing well in terms of knowledge you also have to prepare about costumes:
- You should wear simple, casual clothes and make you feel confident and show that you respect the other person as well.
- You can also make up lightly but avoid making up too bold and flashy.
Before going to the interview, you should learn about the company and prepare questions to ask the interviewer. Some questions may ask:
- Give me job description in detail, powers, responsibilities and job placement KPA
- Issues the company is prioritizing for implementation and joint implementation plan
- How does getting into an employee’s company require knowledge, skill, and attitude?
- Who do I report to and how to manage it?
- How does the company expect me to perform in the first 90 days?
- Issues that you have to pay attention?
- How does the company work in teams? What is your request?
- I want to stick with the company for a long time, so can you give me some advice on the long-term development direction?
- During the interview, could you give me a little comment about yourself?
The bonus for you when you ask an employer is that you are very interested in this job and interested in this company.
2. When interviewing
- When interviewing, do not ask the interviewer what questions you should answer, but we should expand the issue on the condition that we are sure because mostly the interviewers will rely on your answers to them. Ask the next question for you. Based on this, the employer can know if you understand the problem deeply or just through the speaker.
- Speak moderately enough to sound like sharing or speaking normally.
- Answer focused and direct to the question.
Above, I have just presented some questions and suggested how to answer that question along with some tips I have learned and accumulated during my interview. We hope to be helpful for you 
.