“ Behavioral Question”

1. Suppose you find a bug in production. How would you make sure that the same bug is not
introduced again?

Add uncaught functionality to regression test cases, so same bug is not introduced again. If I have
Automated Regression suite, then I write a new script which validate the functionality.

2. What do you do when your developer denies that what you filed is a bug?

Provide Business Documentation reference to support why the existing functionality is not as per design.
Involve PO/BA for discussion.

If bug is not reproducible, then provide screenshots of the bug, give timestamp on when you
reproduced this so that developer can check application logs. Provide test data I have used for
replicating the issue.

3. What has been one of your greatest challenges while doing regression testing?

Test data issue- data runs out when I repeatedly use the same test data. Credit card balance when it
goes to zero, then have to add the balance again.

Improper selection of regression test cases might skip a major regression defect to be found. If I miss
any major defect, then it will go untested when released. It wasn’t tested because it was not part of the
suite.

4. Difference between functional and non-functional testing?

Functional testing verifies that features/system is working as expected according to requirements

Nonfunctional requirements: how well the system does it within design and resource constraints.

5. Enlist some of the key challenges that are faced while performing software testing.

Test Data Issues

Environment available - developers working on 3 different stories, each qa has to wait for the
environment to be available. Then the test gets delayed, time management issue.

Using right set of tools- in the beginning stages, get the right tool

6. What are the different levels of testing?

Unit testing- done by developers

Integration testing- whether 2 modules are successfully connected. API testing

System Testing- make sure application is working as expected

7. What are the drawbacks of the agile implementation/methodology that you faced?

Sprints are usually very deadline constrained

Frequent change in requirements

8. What is your approach when you have a high priority release to be delivered in a very short time?

Run automation suites- run the failed test cases

Run unit tests- testing only code. Make sure all code is tested.

Manual testing on high level priority business test cases.

9. Give an example for high priority low severity bug.

Wrong logo image on application

High severity -> cannot perform any function in application, blocked from everything. Low severity ->
can still perform critical functions.

Priority -> what order should be fixed.

10. What is a test plan?

It is a document that consists of scope, approach, resources, and outline of the testing project as well as
the activities for tracking the progress of the project.

11. What will be your reaction if a project you work on got sudden change in deadline?

I am open on my thoughts if I can deliver the project with QA sign off covering all test cases

If a pre release is must, then discuss the opportunities of increasing QA resources or possibility of partial
product delivery

I have the power to hold QA sign off if I am not satisfied with quality of product which eventually stops
the release date.

12. How do you select regression test cases or form the regression test suite?

Include the test cases that verify core features of the application.

Include the test cases for functionalities that have undergone recent changes.

Include the test cases that have frequently yielded bugs.

13. What are your daily activities as a member of automation tester in your office?
Attend daily stand up meeting. Then if I have any question, discuss offline with developers or BA. Check
email for the status of jenkins test run. 90-95% passed but if failed, fix and run the failed test cases.

Check my emails and reply on time.

If there are any sprint planning, or grooming meeting, I will attend.

Run smoke suite on daily basis and send mail to team on health of application. Send them the report.

Finish the tasks assigned to me. Update the task to the team members.

Verify defects assigned to me and take appropriate actions.

Work on manual and automation testing for stories in current sprint.

14. Have you ever managed writing test cases without having any documents?

In one of my previous project, there was an internal tool that needed to be re-developed with new
technology, but there were no test cases/documentation for the old/existing product. Since there is no
documentation, I had to understand and explore the existing product to come up with scenarios. I spent
time with PO and seniors to understand the business of the tool.

Going through production bugs which was found previously for product so that edge test cases are not
missed in writing the tests for upgraded product.

15. What is the first action you perform as a tester when application throws errors?

First I check the console to read the error message.

Then I open the network tab in my browser and see if any request responses are failed.

Then I verify application logs to understand the actual issue.

16. How do you solve if there are any conflict with your peer QA on any technical aspect?

There should be argument only up to certain extent with my peer on why I am correct. If there is still
conflict, I involved the team and discuss the conflict issue with larger audience. I am open to take
suggestions from my team. I can accept any decision made from team meeting with a smile.

17. How do you decide if a test case is not ideal candidate for automation?

Tests which are highly dependent on data with frequent changes every time.

Tests which cannot be automated due to technical challenges like captcha or bar code

Tests which are unstable due to complex nature of application.

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

Regression testing is to ensure that changes have not affected the unchanged part. Regression testing is
not carried out for specific defect fixes.

19. What’s the most interesting bug that you’ve found recently?

Using the same link for orders for 2 separate accounts. There is a flaw in the logic of the application. You
should get a message that says you are not authorized to see the order details for the account but same
link was working even though the user did not have access to the resource.

20. How do you differentiate dummy login page which is exactly designed like your working project
login page?

Check the application logs. The dummy should not be logging the application vs the working project
should log everything.

21. How will you tell if enough test cases have been created to test a product?

Each requirement is mapped to at least one test scenario.

Each test scenario should have positive and negative test cases.

Using RTM to check whether these test cases are covering all the requirement specification.