Explore topic-wise InterviewSolutions in .

TWO parameters required to CHECK the quality of test execution includes: 

• Defect reject ratio: Ratio of total rejection to total production.
• Defect leakage ratio: Ratio of the total POSSIBILITY of rejection OCCURRENCE to the total production.

CONFIGURATION testing is a software testing technique that is used to evaluate the configurational requirements of the software. It DISCOVERS the optimal configuration of the SYSTEM under which the application performs at its BEST, therefore configuration testing is considered important. It ALSO helps in identifying and resolving any compatibility issues. 

Pesticide paradox is basically a PHENOMENON where the more one tests the software, the more it becomes IMMUNE to its tests. To overcome this, testers should always find new STRATEGIES, approaches, and test CASES, so that they can identify bugs and resolve them. 

SMOKE Testing: It is a type of testing performed to ensure that the acute functionalities of the program are working well. It acts as a confirmation of whether the QUALITY assurance team can further proceed with testing or not.  
Sanity Testing: It is an unscripted form of testing performed to ensure that the code changes that are made are working well. It is performed by the test team for some basic tests. This testing focuses on ONE or a few areas of functionality and is usually narrow and deep. 

Smoke vs Sanity Testing: 

The EXPERIENCE-BASED TESTING technique is a type of testing that is based on the tester’s experience with testing to understand the essential AREAS of a system. This type of testing is generally used in a low-risk system. Individual’s information, abilities, and foundation knowledge are prime supporters of the test conditions and experiments in experienced-based techniques. There are four different experienced-based testing techniques as SHOWN below:

Defect life cycle, also known as a bug life cycle, is a life cycle of various stages through which a defect goes during its whole lifetime. This life cycle starts as SOON as the defect is DISCOVERED or reported by the tester and ends when the tester ensures that the defect is RESOLVED and it won't OCCUR again. The defect life cycle includes the STEPS as shown below:

Test scenario also called a scenario test, is defined as high-level detailed documentation of test cases or use cases. In this, the TESTER tests the software application from an end-user perspective. It USUALLY can SERVE as the basis for lower-level test cases or use case creation. Test scenario is also known as test condition or test POSSIBILITY. It gives you an idea of what we need to test.

Test Harness: Test harness, also known as the automated test framework, is a collection of software and test data required to UNIT test software modules during development. It is mostly used by the developers and helps in the automation and EXECUTION of unit test CASES. It generally includes two main parts as given below: 

• Test execution engine 
• Test script repository

Test Closure: Test closure is basically a document that provides the summary of all the tests that are performed during SDLC. It gives full detailed analysis REPORTS of the bugs that are discovered and removed. It is USUALLY performed prior to the end of the testing process.

Some of the most POPULAR INTEGRATION TESTING TOOLS include: 

• DBUnit 
• Greenmail 
• Mockito 
• REST-Assured 
• JUnit 5 
• H2 Database, ETC. 

• BIG BANG TESTING 
• Bottom-Up Testing 
• Top-Down Testing 

System Testing: It is a typical black box testing technique that is PERFORMED in a complete and fully INTEGRATED system to evaluate the system’s compliance with its specific requirements. It must investigate both functional requirements and non-functional requirements. Generally, it is performed by both testers and developers.

Unit Testing: In unit testing, each component of the software is individually tested. Generally, unit testing is performed by developers. Those systems that have a lot of interdependencies between their modules cannot be tested by unit testing. 

System vs Unit Testing:

Regression Testing: Regression testing, also known as generic testing, revolves around re-running functional and non-functional tests. It is especially DONE to ensure whether previously developed and tested software STILL performs the same after a change or not. It can be performed either manually or using automated tests.

Re-testing: Re-testing, also known as planned testing, is used for specific bugs after it has been fixed by the developers. Re-testing is performed to CHECK the SCENARIO under the same environmental conditions after detection has been fixed. 

Regression vs Retesting:

A/B testing is the process of testing two or more different versions of your software with users to assess which performs better. It is a low-risk way of testing variations of a new or existing functionality.

You can choose a PART of your users to use feature A. The other group uses feature B. Then user FEEDBACK and response are evaluated using statistical testing to decide the final version of the feature. 

Typically, A/B testing is used to test the user EXPERIENCE of different INTERFACES. This allows the team to quickly gather feedback and test their initial HYPOTHESIS.

It’s a process of automatically testing a web application’s FUNCTIONALITY in a BROWSER, where a program launches the browser, NAVIGATES to the application, and interacts with the user interface by clicking buttons or LINKS, just like an average user would.

The only difference is that the browser automation can test this very quickly and often, WHEREAS the same test would take a human tester a long time. It’s part of automated testing. Some essential tools for browser testing include Selenium, protractor.js, and cypress.

Test coverage is a metric that indicates how much of the source code is covered by the tests, allowing the tester to VERIFY the quality of their testing. It helps the tester figure out whether they are testing everything they're supposed to test.

Test coverage can mean different things to different people, depending on the particulars of their testing approaches.

1. Product: It means LOOKING at test coverage to answer the question: Which features or the areas of the software does your tests cover? 
2. Requirements: The software might work well, but it's not useful to the CUSTOMER if it doesn't SATISFY their needs. Requirements coverage indicates how many of the requirements are TESTED. 
3. Source Code: This is usually a developer's domain and is a white-box testing technique. The developer can check how much of their source code is covered by the unit tests.

An HTTP status code is a three-digit number that indicates the status of an incoming HTTP request, that is, if the request has been completed or not.

A server can send the following five types of responses for an HTTP request.

1. Information (100 - 199): These status codes PROVIDE a temporary response. The response consists of the status line and optional headers and terminates by an empty line. 
2. SUCCESS (200 - 299): Indicate that the incoming HTTP request was successfully RECEIVED, understood, and accepted. 
3. Redirect (300 - 399): These status codes indicate further actions the client should take to satisfy the HTTP request. It can mean that the requested resource may have moved temporarily or permanently. It can also redirect the client to another URL. 
4. A client error (400 - 499): Indicate a problem with the client who INITIATED the HTTP request. 
5. Server error (500 - 599): The 5XX status code indicates a problem on the server while processing the request. 

API STANDS for Application Programming Interface. It is a means of communication between two software COMPONENTS. An API abstracts the internal workings and complexity of a software program and allows the user of that API to solely focus on the inputs and outputs required to use it. 

When building software, developers rarely write software from scratch and MAKE use of other third-party libraries. An API allows two software components to talk to each other by PROVIDING an interface that they can understand.

Another use of an API is to provide data required by an application. Let's say you are building a weather application that displays the temperature. Instead of building the technology to collect the temperature yourself, you'd access the API provided by the meteorological INSTITUTE.

In SOFTWARE, many errors occur near the edges of the range of the data values. For example, when the programmer uses the greater-than OPERATOR (>) instead of the greater-than-or-equal-to (>=) operator, it causes the off-by-one indexing error.

Typically, developers miss these boundary cases because they follow a happy PATH when DEVELOPING and testing. Boundary value analysis helps to discover the errors caused by extreme values. The tester chooses the test data at and immediately above and below the boundaries of the input domain of the data.

For example, if an input field expects a string of 20 characters long, the tester tests it with STRINGS of lengths 19, 20, and 21. 

Selenium is a web browser automation tool that automates the test suits you need to run on a web browser.

Some of the benefits of Selenium include:

• It is open-source software, eliminating licensing COSTS. 
• It supports all the MAJOR languages, such as JAVA, C#, Python, Ruby, ETC. 
• It supports all the major web BROWSERS, e.g., Google Chrome, Firefox, Safari, etc. 
• You can integrate it with other testing frameworks and tools to build a comprehensive test suite for your software.