SOFTWARE TESTING- INTERVIEW QUESTIONS AND ANSWERS

21 Sep 2020

SOFTWARE TESTING- INTERVIEW QUESTIONS AND ANSWERS

1.What is sign off process how it is followed in your company?

    1. Sign off is given by Test Manager at the end of the Sprint.
    2. Sign off is given once Test Manager is satisfied with the test coverage and test goals have been achieved. All the SIT testing, performance testing, Regression Testing(manual or via Automation suite) is completed. All the defects have been fixed and retested. Exploratory testing is completed.
    3. Once all the above is completed Test Manager sends an email indicating that “we have done all forms of testing and now QA team can say to a considerable degree of confidence that release is bug free”
    4. Its a “go-ahead” from QA team side.
    5. Sign off activity happens after end of each sprint.
  1. What is User acceptance testing ? and what is the UAT criteria?
    1. UAT testing is a mechanism by which actual user or client make sure that what ever was promised is delivered.
    2. It happens after the test cycle.
    3. In few cases its not even part of Sprint and happens as a separate activity after test manager signs off the code base.
    4. In UAT primarily user stories of the current release is checked.
  2. What is a Smoke test and what type of test cases are included in your smoke pack?
    1. Smoke test is a way of validating the stability of the application.
    2. We run smoke test usually just after the deployment, to check if application is stable enough to start further testing activities.
    3. Smoke pack usually checks ‘end to end’ and top functionalities of the application.
    4. For example in the case an e commerce application, Smoke test would have these test cases:
      1. Check the URL
      2. Login
      3. Search a Product and add to cart
      4. Check out the cart
      5. Place Order and validate the price, quantity etc
      6. Validate the Payment gateway API
    5. Smoke test should be automated.
    6. Automated UI Smoke test pack should not take more than 10 mins to execute.
  3. What type of test cases included in your regression pack?
    1. We have a total of 1000 test cases.
    2. Out of 1000 we have automated around 700 + test case in a period of 1 year.
    3. Our regression test pack usually contains all the priority test cases.
    4. In each sprint we automate only the priority test cases from a list of Regression test cases.
    5. We execute these 800 test cases via our automation test pack.
    6. We are using test ng parallel execution feature. So, our Automation pack takes 5 to 6 hours to execute.
    7. Remaining test case are executed manually.
    8. Manual team usually only executes non-automated priority test cases
    9. Other than that we also do 1 day of exploratory testing just before sign off.
  4. How frequently do you execute the regression pack, its either a daily basis or weekly basis?
    1. Every 2 day we have a new code deployment during the sprint.
    2. We run our regression pack every 2 day i.e. as soon as new code is deployed.
    3. As soon as new code is deployed, we executes Smoke automation pack first and with in 10 mins we get to know if code deployment is successful or not.
    4. If smoke test results are green then we manually trigger full regression pack on Virtual Machine.
    5. So in a single sprint, which is of two weeks for us, we execute the regression pack at least 4-5 times in 2 weeks.
  5. What is the pipeline structure of Jenkins for execution of test packs?
    1. We are using Jenkins for Continuous Integration.
    2.  Jenkins is primarily responsible for building the application code. Steps in CI typically goes like this in our project:
      1. Developer merges their code in to master branch of Git.
      2. Jenkins continuously polls or reads application Git master branch.
      3. As soon as there is new commit on application master branch, Jenkins triggers the Build process.
      4. Jenkins downloads the application code(in  java, C#) etc and deploys the application code on the Test server.
      5. Jenkins also would execute the Unit test before the deployment.
      6. Then Jenkins Would go to the Selenium automation Git repository.
      7. Jenkins then read the master branch of the repo and create automation code build
      8. It then executes the test using maven sure fire plugin and TestNG.
      9. We first run Smoke tests pack via Jenkins, to test the Stability of the application.(However, you can run full regression as well)
      10. Once the execution is completed, Jenkins will email the report to all the stake holders.
  6. How nightly execution is executed via Jenkins who triggers it and how the reporting is generated and sent to the respective persons? What is included in the reports.
  7. How you configured Jenkins?
  8. When you started the automation testing after the project started(after how many days,what’s the reason of delay in starting automation procedure )?
  9. What if the requirements are fixed and customer needs an agile environment for testing?
  10. How you are integrating maven with Jenkins?
  11. How you are integrating maven with eclipse?
  12. What if maven is not used then is it possible to build a project without any tool and deploy it or distribute it?
  13. How you integrate Git with GitHub?
  14. What is .bat file? Where you are using it?
  15. How to reduce maintenance of our framework?
  16. Suppose if your release is @6 pm  n before 2 hrs major blocker bug arises at client side then what should u do? And development team wants 2 days time to develop or Fix that issue?
  17. What is non reproducible bug? How to raise it to the developer team as it doesn’t get reproduced quite easily.
  18. If there is a verification module link and that is expired after 24 hrs and after link expired you have to automate or test it, then how can u automate that expired link?
  19. If 1 module or test cases tested 5 times but 1 bug is there  and the whole project is retested already then how to handle that situation?
  20. What is scrum? Explain roles ?
  21. What is risk analysis?
  22. Suppose you have 100 test cases and you want to run within 1 hr,then what should you do?
  23. After automation testing completed assume that new requirement have been added how will you handle this in automation.
  24. What is the design factors should been taken into consideration while creation of framework.
  25. When you get the bug what is your approach.
  26. What are the qualities you should have for becoming a good test engineer?
  27. What is difference between test data and testing data?
  28. When do you interact with BA and for what reasons?
  29. Do you ask for a code freeze date for Dev Team?
  30. How deployment process works,and explain continuous integration process,how to make a build using jenkins and how to test it on your environment?
  31. internal working and flow of your FW?How to perform database validation at backend process?
  32. On what basis you decides priority for test cases.
    1. Realistically, its the manual team QA, BA or Scrum master determines the priority of the test cases.
    2. Usually, all the requirements are in the form of User stories kept in jira.
    3. All User stories have to have priorities and certain level of importance mentioned in the Jira itself.
    4. So when you create test cases out of User stories they also inherit the same priority from their user stories or epics.
    5. Higher the priority of user stories , higher the priority of the test cases.
    6. Priority is mostly decided based on the how risky the feature/functionality is. By risk I mean, if a defect is not caught in the feature/functionality what and how much the client/company lose.
    7. For example, take a case of an e-commerce application like amazon. Imagine there are two test cases.
      1. Search a product and check filters are correctly displayed.
      2. Search a product and check prices are correctly displayed.
      3. Check all the categories are displayed in the menu item.
      4. Check payment gateway window appears after user clicks “place Order”.
    8. Lets decide the priority of above cases.
      1. Any defect after the execution of above scenarios is bad, no doubt about it. But their impact would vary.
      2. Test case 3 is lowest priority.
      3. Test Case 1 and 2 will have Medium priority.
      4. Test Case 4 will have Highest priority as this will have direct financial loss to the company.
  33. What is drawback of your framework?
    1. Current drawback is that in the way we have implemented the logs and reporting. Currently since we using test ng framework, we are using the testng Reports for logging and reporting.
    2. We have around 1000 plus test cases, so the problem which we are facing is that our report becomes very bulky when we try to send it to client, as it contains low level logs and high level logs both.
      1. Low level logs: Element clicked, Screen shot taken, Element is set with value as  John etc. These logs does not make sense to end customer, who is only interested in knowing test case pass and fail status.
      2. High Level logs: Number of test cases passed and failed, what is passed and high level detail on the step it failed etc. Client should only see this.
      3. Solution: We are trying to implement log4j2 for low level logs and Extent report for high level logs. Since we are having 1000 test cases it’s going to be little cumbersome, but we have started implementing the concept now.
    3. Another challenge can be that we are not able to run failed test cases programmatically. To solve it, we are trying to implement test ng interface (Nivedita will write its code)
  34. What is recovery scenario and how will achieve ?
    1. Recovery scenario is being handled via Exception handling in java. It is used to get out of un-expected errors which might come during the execution.
    2. We have good exception handling in al most all the important methods. So as soon as any method encounters an error, proper message is logged in the report and test case moves on to the next test cases.
    3. Another example is of StaleElementException. Some times due to dynamic pages with java script code we get StaleElementException. This is not really an application issue, but we need to give our script enough tolerance so that if stale element occurs our test case should not fail but rather capture the exception and retry the step.

      In short thats how we implement recovery scenarios in our project.

 

 

Courses

View all