SDET Interview Questions & Answers

5 avg. rating (100% score) - 2 votes

SDET Interview Questions

    1. Question 1. Explain Differences In Details Between Software Development Engineering In Test (sdet) And Testing Software Manually?

      Answer :

      SDET is mainly using doe automation testing. Means develop a product can be tested automatically without manual intervention. Whereas manual testing is not at all meet these criteria.

    2. Question 2. Explain Details Explanation Of The Job Responsibility Of A Tester Or Software Development Engineering In Test Role?

      Answer :

      This is the common SDET Interview Questions asked in an interview. Several responsibilities normally need to follow by an SDET tester in current IT industry.

    3. Question 3. Normally There Have Different Category Available To Make One Specific Group By Of Varieties Test Cases, Given The Explanation Of Them?

      Answer :

      Some popular test cases in the current IT industry are below:

      • Functional testing
      • Frontend or User interface testing
      • Performance Testing
      • Integration testing
      • Load testing or User usability testing
      • Security testing

    4. Question 4. What Is Risk-based Testing?

      Answer :

      Risk-Based testing is defined as the functionalities of a product are tested based on the priority of the deliverables. Risk-Based testing includes testing of crucial features of a product which will have a business impact and the probability of the failure of those features is very high. The priority for all functionalities of a product is set based on the business requirement then the high priority functionalities will be tested first then medium and then low priority functionalities. Risk-Bases testing will be performed when there is no sufficient time to test all the functionalities of a product.

    5. Question 5. Explain In Detail About Different Kind Of Testing Called Alpha And Beta?

      Answer :

      Alpha testing done by the tester, it identified bugs before moving the product to live environment or to the end user. The beta bug is normally identified by the end user who is the actual users of the product or application.

    6. Question 6. Write A Program To Reverse A Number In Any Language?

      Answer :

      public class reverse Number {

      public long reverse(long num)

      {

      long temp=0;

      while(num!=0)

      {

      temp=(temp*10)+(num%10);

      num=num/10;

      }

      return temp;

      }

      public static void main(String args[])

      {

      long n= 654312;

      reverse Number in = new reverse Number();

      System.out.println(“Given number is “+ n);

      System.out.println(“Reverse of given number is “+inp.reverse(n));

      }

      }

    7. Question 7. Explain In Details How We Can Define Ad-hoc Testing In The Current It Industry?

      Answer :

      The ad hoc testing is one of the testings very much popular in the IT industry. This kind of testing mainly unplanned and without documentation. It normally need to perform when some ad hoc requirements come from the client, the developer has to develop the same in a priority manner.

      Now tester needs to test it immediately and come with proper deliverables in the very small period of time. Documentation or planning is not always possible for that, but some of the organization maintained some specific tools for tracking this kind of task especially for additional billing.

    8. Question 8. Two Big Keywords Normally Very Much Useful For The Tester, One Is The Priority And Another One Is Severity, Explain The Difference Between Them In Details?

      Answer :

      Priority and Severity both are very important two keywords in the IT industry, especially for those organization who have involved in production support activity of their provided product or any existing system of the client. Currently, all the bog organization tried to follow one specific tool where one helpdesk team has been assigned for handling. Normally end user reached to that corresponding helpdesk team for raising their concerns or end user can able to create their concerns directly in that specific tool.

      Some helpdesk person first analyzes the same then given the priority based on the end user impact. Helpdesk person, tester, developer and some point of time business analyst involve with that issue and try to understand what the exact impact of that specific issue, based on that they have given severity of that issue. So priority defines how much important of that issue is, and severity is defined impact or destruction ability of that issue.

    9. Question 9. What Is Ad-hoc Testing?

      Answer :

      • Ad-hoc testing is defined as the testing is being done on an ad-hoc basis without any reference and proper inputs to the test case and without any plan, test cases, and documentation. The main objective of this type of testing is to find defects and break the application by executing different flows of the application or random functionality.
      • Ad-hoc testing is an informal way of finding bugs from an application and can be performed by anyone in the team. It will be difficult to find bugs without test cases but sometimes during ad-hoc testing bugs will find which we didn’t find through normal testing or existing test cases.

    10. Question 10. Given Some Example With Details Regarding Some Of The Typical Experience Or Excessive Load Working Day Of A Tester Or Software Development Engineer In Test (sdet) Resources?

      Answer :

      Three key tasks are always taken huge time for the tester in any day:

      • Understanding the requirements of the project.
      • Preparing and executing require test cases based on the client expected functionalities.
      • Reporting about the bugs identified on individual functionality developed for the client to the developer and retest the same after redelivery by the developer for ensuring expected functionality properly deliver without any common bug.

    11. Question 11. Explain About Some Expert Comments Of How One Tester Can Decide That Provided Product Are Actually Ready To Move In The Live Environment?

      Answer :

      This is one of the critical decision, so it never been taken by the single person or junior guys. Only developer and tester are not involved for taken this decision, higher management is periodically involved in that.

      Management test mainly ensure by validating below for ensuring product delivery are bugless:

      • Validating bug report provided by the tester. How bug got resolved and retesting done by the tester or not.
      • Validating all the test cases written by the tester for that specific functionality, documentation, and confirmation taken from the tester on the same.
      • Run automate test cases for ensuring new functionalities does not break any existing functionality.
      • Sometimes validating test coverage report, which ensures all the developing component has been covered by test cases written.

    12. Question 12. Write A Program To Swap Two Numbers Without Using Any Temp Variable?

      Answer :

      Program to swap two numbers without using any temp variable is as below:

      public class swap{

      public static void main (String args[])

      {

      int x = 20;

      int y =30;

      System.out.println(“Numbers before swapping”);

      System.out.println(“ number x is “ + x);

      System.out.println(“number y is “ +y);

      // Swapping numbers

      x= x+y;

      y=x-y;

      x=x-y;

      System.out.println(“Numbers after swapping”);

      System.out.println(“ number x is “ + x);

      System.out.println(“number y is “ +y);

      }

      }

    13. Question 13. If Someone Needs One Specific Format Of Bug Reports From A Tester, Then What Will Be The Best Way Or Approach Can Take By The Tester For Providing The Same?

      Answer :

      One bug report normally contains below:

      • Bug Summary
      • Reproduce steps
      • Expected behavior and current behavior of one specific bug.

    14. Question 14. Common Challenges One Software Tester Normally Faced, That Is Proper Documentation Not Maintaining For Testing. In That Case How We Can Overcome The Same?

      Answer :

      It is one of the common scenarios where documentation is not properly available for all kind of test cases, but the requirement has to fulfill and deliver the same to the client on time. In that case normally tester are following some client provided mail where describe all the requirements properly, if possible screenshots of the application where those parts of changes clearly mentioned, or some Mon or verbal telephonic discussion done with the client for understanding exact functionality of that changes which is enough for testing quickly and deliver the same in expected timeline.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Software testing Tutorial