Explore topic-wise InterviewSolutions in .

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.

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.

One BUG REPORT NORMALLY contains below:

• Bug Summary
• Reproduce STEPS
• Expected behavior and CURRENT behavior of one specific bug.

One bug report normally contains below:

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);

}

}

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);

}

}

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.

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:

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.

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

• 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.

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.

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.

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.

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.

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));

}

}

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));

}

}

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.

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.

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

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

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.

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.

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.

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.