Possible Questions Flashcards
What API methods are you familiar with?
GET - retrieve data
POST - submit data
PUT - update existing data
PATCH - update partial data
DELETE - delete data
What API testing/tools clients are familiar with?
Postman
Swagger - also has API client inside of it
How do you authenticate yourself in Swagger?
You will have to use a token
Why do you need to authenticate in Swagger?
You need to show that you have the permission, or credentials to access the data
What is the DOM?
- Document Object Model
- It represents the structure of a document as a tree where each node in the tree represents a part of the document, such as an element, attribute, or text
- It provides for a way for programs to dynamically access and update the content, structure, and style of HTML documents
- You can execute code in the DOM
What is the difference between a for loop and forEach method?
- For loops - can be used to iterate over arrays, you have more control over the loop’s behavior with explicit control over the initialization, condition, and increment
- forEach - higher order function available on arrays, it iterates over each element in the array, and executes a provided function once for each element, provides a cleaner syntax for iterating over arrays
Summary: For loops offer more flexibility and control over iteration, while the forEach method provides a more concise and readable way to iterate over arrays specifically
What do you use to see API requests in browser dev tools?
Inspect element -> network
How do you see only API requests in network tab?
Click on the ‘Fetch/XHR’ button
What is the difference between PATCH and PUT?
They are both used to update data, PATCH updates part of the existing data, PUT updates the entire existing resource
What if you are the first QA in a company?
- Learn application - First, what requirements do you have? Go through documentations, design templates, and whatever else. If there are no documentations, go through JIRA, meet with people in the engineering team to learn about the app from their perspective. What was last built, what is being built right, and how do they like the process
- Start supporting the most critical part, which is usually release - standardize list of scenarios, start automating most critical test cases
- After documenting test cases and working for about a month, start negotiating improvements with team
What are the steps to automate from scratch?
- We would have to look at how much resources we have to start automating, what can we pay for?
- Timewise, what’s the quickest framework we can use to automate
- Then we dive into requirements and understand what we have already automated, what frameworks are already in place and we need to migrate them
Does it matter what language you use in the automation framework?
It doesn’t have to be the same language they’re using, so its easier to go with what I’m already familiar with
How good are you at automation?
I was able to build a simple framework from scratch, write some UI automation test cases, I utilized the POM…
I show them what I’ve done, and let them judge based on that
What is a good test case?
- Steps are clear and concise
- Focus on end-user requirements
- Avoids repetition
- Steps are easy to understand and execute
- Self-cleaning
- Returns the same result no matter who the tester is
Conflict with teammate?
I don’t want to get anyone in trouble, I just want the work issue resolved.
I would reach out to the person directly, to see where they are coming from. Or I would reach out to the manager to get advice.
And I try not to take things personally
How do you approach testing requirements that are incomplete or unclear?
- The worst thing to do is go with my own assumptions
- I’ll try to get it clarified, so I’ll go to the PM, or QA lead, or whoever has those requirements and can clarify
How to prioritize tests when there are competing demands?
- I always have a list of priorities and they are ranked, and I work on a top-down approach, taking into consideration critical functionalities, or release time
- If there isn’t any time for lower priority items, I can try to get help from other team mates
- Another way is to bring it up during the daily sync meetings, if priorities are changing often
Difficult decision during testing
- Everything comes down to priority
- What makes the company the most money, what are the most critical functionalities
What do you do if you are the only person who found a bug and gets to decide if you should go through with release?
- Ultimately, I would try to assess the risk
- If it affects a critical functionality, I would not go through with release
- If it’s something low priority/ low severity, then we can ship it
Conflicting priorities/expectations from different stakeholders
I’ve never had this happen to me, but if I ever did, I would get the two stakeholders together and have them figure it out
Difference in opinion between you and a dev or product owner?
- I would reach out to the person directly, maybe schedule a meeting
- I would try to explain why I hold my opinion and advise them, but ultimately they make the decisions
How do you approach testing a product with a large number of features and/or complex functionalities?
- Test planning really is the core
- Test cases
- I won’t be able to remember everything, that’s why there’s a case management system
- I would consult with team members as well
How would you explain things to a non-technical stakeholder?
- I would try to explain things in simple human language using non-technical terms
How do you make sure testing is comprehensive and convers all possible scenarios
- I use a test matrix, which describes which tests cover which functionalities
- I would ask a QA from a different team to take a look at the product and see if anything was missed, it helps to have a new set of eyes
How do you manage time with limited testing resources?
- I would just let my team mates I have limited capacity
- If it’s an urgent matter, I would reach out to the QA manager/ lead to get someone to help
- For sure, I would not promise more than I can do
Can you speak about a time when you had to work under pressure to meet a tight deadline
- I don’t mind putting in extra time and effort for the sake of my team, to make sure things get done in time
- It helps that I stay organized, because it’s easy for things to get frantic with tight deadlines
- It’s also important to be mindful of maintaining quality, especially for features/components that are critical, so we can take our time with those
What is your approach for testing new technology or unfamiliar testing tools?
- I would just get into it and start testing. The best way to learn for me is to try and use that app
- I would consult with a teammate and see what’s different between different tools
- Read official documentation, watch YouTube videos
How do you investigate a reported issue that was difficult to reproduce?
- I would do my best to understand the issue, get as much information as possible
- Double check with the person who reported the bug
- If that person is not there, talk to the PO, dev, or QA teammate who knows the product better than me
- If it’s just a one-off thing, it’s not worth it to waste too many resources on it
How do you ensure that your testing is in line with overall product goals and user needs
By making sure that I am testing according to the requirements
Can you speak about a time when you had to manage conflicting priorities with your testing team?
- Communication is key
- I will let them know that I have my own priorities, but if needed, I can put in some overtime
- And if I really cannot do what they are asking of me, I would just let them know
A time when you had to test a feature that was controversial or potentially problematic
- The conversation should have happened during the sprint planning meeting, with PO, or PM, way before testing
How do you ensure your testing is efficient and does not result in duplication of efforts
- Communication
- Check JIRA board and see what each person is working on
- I would also specify during daily sync meetings
- Could possibly involved improving testing process of QA team
How do you ensure your testing is scalable and can handle increased user traffic and volume
Performance testing and load testing
How do you prioritize your work as the main QA engineer?
- Through organization and assigning priority
- You want to make sure when you’re preparing for release, and you have to pick and choose you can refer to your documentation for priority
- And if that is not indicated in the test case management system, you have to use your judgement as a testing expert
What is your approach to collaborating with devs during the testing process?
- Through JIRA tickets, comments tag dev
- Open channel in slack
What are the QA processes?
- Testing functionalities
- Verifying functionalities
- checking for bugs
- Writing bug reports
- Writing test cases for tickets
- Automating those test cases in an order that makes sense
- Writing documentation for the team
- Helping to improve the efficiency, maybe looking for a better framework
- Joining meetings
Why are you leaving your current company?
- I had a contract with the company, and it is expiring
- I learned a lot, but now I feel like I’m ready to learn more and step up
