Technical

Question 1

What are your tasks and responsibilities on a daily basis ?

Answer 1

1Attending various meetings

Fundamental testing process
Review/ analyze requirements
Create test cases (positive, negative, edge cases)
Execute test cases
Report results
Create bug reports, connect with devs to perform root cause analysis of bugs and findings solutions.

Finding automation candidates to convert into automation test scripts

Question 2

What is your team size in your current position?

Answer 2

3 dev : 1 QA

Question 3

What type of software testing are you performing at your current position?

Answer 3

database, automation, api, integration, regression, smoke, black box testing (functional), UAT testing, performance (Jmeter, loadrunner), accessibility testing

Question 4

Are you familiar with writing test documents?

Answer 4

Test plan(project) , test strategy (Company), Test cases, RTM, Bug reports

Question 5

What are the components of your test cases?

Answer 5

Test case name, unique identifier, pre-conditon (expected result), input, description, post condition, out-put (actual result), status (TUPSIDOP)
NEWESP_1900: User should be able to enter a valid credit card number (16 digits)
TC_1900_1: valid 16 digits
TC_1900_2: negative scenario (15 digits)
TC_1900_3: negative scenario (17 digits)
TC_1900_4: negative scenario (alphanumeric values)

Question 6

Does your company follow an agile methodology?

Answer 6

Sprint planning meeting (grooming session), daily stand up, sprint review, Sprint retrospective
Retrospective – better understanding of requirements earlier, process improvements, better communication, better teamwork, asking questions
Scope creep – avoid

Question 7

Can you tell us what is the bug life cycle?

Answer 7

Discovery of a bug 🡪 bug report 🡪 assign to dev 🡪 fix 🡪 re-tested 🡪 closed

Question 8

What are some best practices you follow when reporting bugs?

Answer 8

We try to reproduce the bug atleast 3 times, we can ask another QA to reproduce, re-reading the requirements, re-reading bug report, write a clear bug summary that describes the steps to reproduce the bug, severity of the bug, Version: 2.3, operating: windows, browser (chrome, firefox), screenshot (bug), always one bug per report

Question 9

Tell us about a difficult situation you encountered and how you overcame it?

Answer 9

Automation- not having unique locators
Spoke to devs – requested them to add unique locators to elements
Used dynamic xpaths to locate elements
Not having accurate time estimates – sometimes features are complex, sometimes it’s a new feature.
Not having enough time to test
Prioritized major functionalities to test first
Spoke to the team to find a solution so proper testing can be done
And then noted better estimates for the future
You reported a bug, dev did not acknowledge it as bug
You first verified if it was reproducible
Then you set up walk through meeting with devs to reproduce the bug
You can set up meeting with PM, PO to discuss the correct functionality of the feature

Question 10

Tell us about a time you had a disagreement with a team member and how did you resolve it?

Answer 10

Deadline and estimates (PM, Scrum master)
Testing rushed- not able to test all possible scenarios, possible bug leakage
major functionalities, prioritize testing
Extend the sprint, or move the less prioritized stuff to next sprint.

Question 11

What are the qualities of a good tester?

Answer 11

Detailed-oriented, creative tester, thinking outside of the box, understanding requirements, being flexible, coming up with positive and negative scenarios & edge cases, also follow steps and procedure to test before edge cases, good communication, team player, takes initiative, willing to learn.

Question 12

How do you ensure complete test coverage (all requirements have been tested)?

Answer 12

Comprehensive test plan, test strategy, positive and negative test cases to cover all possible scenarios. RTM (mapping between testcases and requirements), to make sure all acceptance criteria have been implemented.

Question 13

How do you determine testing has been complete/ when do you feel comfortable providing a QA sign off?

Answer 13

No bugs, no more requirements to be tested, you thought of all possible scenarios to test, positive negative testing, edge cases, RTM, once the actual results match the expected results, and all acceptance criteria was met.

Question 14

When do you think QA activities should start?

Answer 14

QA should try to get involved from the very beginning of the project or sprint. Review docs, ask questions, get clarifications, think about test cases, provide suggestions and time estimates.

Question 15

Bug leakage vs bug release ?

Answer 15

Leakage – unintentional, missed bug found in prod, unaware
Release – intentional, aware, in prod

Bug leakage – bug is discovered by the end user, unintentional, team is unaware of it
Bug release – QA team discovers the bug, intentional (low priority bugs – it doesn’t have a large impact on the application) these bugs are noted and will be addressed at a later time.

Question 16

Do you think QA’s can also participate to resolve production issues?

Answer 16

When the fix is made, we will have to re-test this. In the future the QA can include this test scenario part of their regression testing to make sure the bug does not reappear again.
Hot fix – prioritize an important bug and fix right away

Question 17

Tell u about bug you found that you were proud of?

Answer 17

In a web application I was testing, there was a feature where users could upload images to their profile. Everything seemed fine during initial testing, but as I dug deeper, I noticed that there was no validation on the file types allowed for upload.
This meant that users could potentially upload files with malicious content, such as scripts or executables, disguised as image files. To exploit this vulnerability, all someone would need to do is change the file extension to something like “jpg” or
“png”.
I reported this issue to the development team, and they quickly implemented server-side validation to ensure that only actual image files could be uploaded. It felt good to catch such a critical security flaw before it could be exploited by malicious actors

Question 18

Tell us about a bug that you missed?

Answer 18

I missed a crucial aspect during QA testing of an e-commerce platform. While focusing on checkout functionality, I overlooked real-time inventory tracking. This led to items appearing available but becoming out of stock before checkout completion, frustrating users. The oversight emphasized the need for a holistic testing approach, considering all system components and interactions to prevent such issues.

Upon investigation, it was discovered that the platform didn’t adequately handle inventory updates during the checkout process. If multiple users attempted to purchase the same item simultaneously, it could result in inventory discrepancies and items becoming unavailable unexpectedly.

Question 19

Supposed you find a bug in production, how would you make sure that same bug is not introduced again?

Answer 19

Add it to your regression suite

Question 20

What is the difference between functional and non-functional requirements ?

Answer 20

Functional – what you what the system to do, requirements about the different functionalities of the application
Non-functional – how the sys actually works under different constraints. Quality attributes
Usability, reliability, performance, availability, scalability

Question 21

What is the difference between functional and non-functional requirements ?

Answer 21

Functional – what you what the system to do, requirements about the different functionalities of the application
Non-functional – how the sys actually works under different constraints. Quality attributes
Usability, reliability, performance, availability, scalability

Question 22

If you do not have documents, what is your approach to testing the software?

Answer 22

Exploratory testing, random testing, play around with the website to understand its features and functionalities, and its E2E process.
Always ask questions for clarifications and understanding more about it

Question 23

cases a week.
In an application currently in production, one module of code is being modified. Is it necessary to re-test the whole application or is it enough to just test functionality associated with that module?

Answer 23

Smoke test = verify the major functionalities 🡪 test the modified module 🡪 associated modules
Test the modified module 🡪 associated modules 🡪 smoke test or regression test of major funcs.

Question 24

What is the difference between white box and black box testing ?

Answer 24

White box- done by devs, knowledge of the code
Black box – no knowledge of the code, testing the UI, regression and functional testing

Question 25

What tools do you use at your current company?

Answer 25

Manual testing: TestRail (testcase management tool), Jira (project management tool)
API testing: Postman API
Database testing: SQL based database (Microsoft SQL server, Oracle SQL developer)
Accessibility testing: Google Lighthouse
Automation framework:
Selenium – automation tool
IntelliJ – Editor
Java – Coding language
Maven – built tool – integrate dependencies, archives
TestNG – testing framework
Performance testing – LoadRunner, Jmeter

Question 26

What is the sequence of testing you follow in incorporating both manual and automation testing ?

Answer 26

Looking at reqs 🡪 manual testing (smoke testing, functional testing, e2e testing, UAT) 🡪 Automated Regression tests 🡪 Push to prod
Then think about automation candidates🡪 automate tests that are good automation candidates

Question 27

What is the difference between re-testing and regression testing ?

Answer 27

Re-testing – retest the defect after the fix was made. — bug is no longer there
Regression – testing other functionalities to makes sure other features are still working and no new bugs were introduced.