Types Of Testing interview questions and answers

Functional testing and non-functional testing are two different types of software testing that evaluate different aspects of the system. Functional testing focuses on testing the functionality of the system by verifying that all the features are working as expected, while non-functional testing focuses on assessing the non-functional aspects of the system such as scalability, performance, usability, security, etc.

Functional testing involves verifying the features and functionality of the system against the business requirements. It ensures the system works as expected and the features are behaving as expected. It is carried out by executing the test cases which are created based on the requirements.

Non-functional testing, on the other hand, is used to evaluate the non-functional aspects of the system. It includes testing scalability, performance, security, usability, reliability, etc. These tests are used to check if the system is able to meet the end-user requirements.

To summarise, the key differences between functional testing and non-functional testing are as follows:

• Functional testing is used to verify the features and functionalities of the system, while non-functional testing is used to evaluate the non-functional aspects of the system such as scalability, performance, usability, etc.

• Functional testing is carried out by executing the test cases which are created based on the requirements, while non-functional testing is used to verify the system meets the end-user requirements.

The purpose of compatibility testing is to ensure that a system or software application behaves correctly when used in different operating environments, hardware configurations, and network environments. Compatibility testing verifies if a system or application can run on different browsers, operating systems, hardware configurations, and mobile devices.

For example, to test a web application, compatibility testing can be done to ensure that it works as expected on different browsers such as Chrome, Firefox, and Edge. Similarly, it can also be used to check for compatibility with different versions of an operating system like Windows, MacOS, or Linux.

The steps involved in compatibility testing are:

1. Identifying the different combinations of operating systems, browsers, hardware, and devices on which the application needs to be tested.

2. Testing the application on each of the combinations to check for any discrepancies.

3. Recording the results and fixing any errors.

4. Retesting the application after fixing any errors to ensure that the application works correctly on each combination.

5. Verifying that the application works as expected on all combinations.

There are several types of testing that are commonly used in software development, including:
Unit testing: Unit testing involves testing individual components of the software in isolation to ensure that they function as intended.
1. Integration testing: Integration testing verifies that different components of the software can work together as intended and that they can integrate seamlessly with other systems.
2. System testing: System testing is a comprehensive testing approach that verifies that the entire system meets the specified requirements and works as expected.
3. Acceptance testing: Acceptance testing involves testing the software to ensure that it meets the acceptance criteria specified by the stakeholders, including end-users and customers.
4. Regression testing: Regression testing is performed to ensure that new changes or enhancements to the software have not introduced new defects or issues in previously working functionality.
5. Performance testing: Performance testing is used to evaluate the software's performance under specific conditions, including high traffic, heavy loads, and peak usage periods.
6. Security testing: Security testing involves testing the software to ensure that it is secure from potential security threats, including hacking, data breaches, and other security vulnerabilities.
7. Usability testing: Usability testing is used to evaluate the software's ease of use and user-friendliness and to identify any issues that may affect the user's experience.
Overall, these are some of the most common types of testing used in software development, and each type plays a critical role in ensuring that the software is functional, reliable, and meets the specified requirements and expectations.

Smoke testing, also known as “Build Verification Testing”, is a process used to ensure that the most important functions of a software program work correctly. It is a non-exhaustive software testing that aims to ensure that the most crucial functions of a program work, but not bother with finer details. The goal of smoke testing is to quickly reject obviously unacceptable software builds, thereby saving time that would be wasted with further testing.

Smoke testing involves testing the major, or most important, functions of a program; such as testing the menu options, buttons, and other major system components. Smoke testing is not an exhaustive test, but is a test to ensure that major functions are working.

Example:
Let’s say you are doing smoke testing on a new software program. You can quickly go through the main menu and test each option. If the program crashes, or an error message appears, then the smoke test has failed.

Steps:

1. Identify the most important functions of the software program.

2. Check major system components (menu, buttons, etc.)

3. Test each option and check for any errors or crashes.

4. If errors occur, the smoke test has failed.

5. If the test is successful, then move on to further testing.

The purpose of regression testing is to identify any changes or bugs in existing or modified functionality of a system or application. It is used to ensure that any new changes or modifications do not cause any unexpected side effects or bugs in the existing functionality.

Regression testing is typically done after the introduction of a new feature or bug fix and can include the following steps:

1. Identify which test cases are relevant for the new feature or bug fix.

2. Execute the test cases to determine whether the existing functionality is still working correctly.

3. Compare the results of the test cases to the expected results to determine whether any regressions have occurred.

4. If any regressions are found, the development team should investigate and fix the problem.

5. Repeat the test cases to ensure the regressions are corrected and the existing functionality is working correctly.

The purpose of usability testing is to evaluate how easy it is for users to interact with a product or application, such as a website or software program. It focuses on the user’s experience and how intuitively they can perform tasks or navigate within the product. Usability testing is often conducted to identify areas of improvement and make the user experience better.

For example, when designing a website, usability testing is often conducted to measure how easy it is for users to find and access information, complete tasks, and navigate from page to page. It can also be used to evaluate user satisfaction with the product, including how enjoyable it is to use.

Usability testing typically involves the following steps:

• Gathering a group of users who match the target audience of the product.

• Setting up a controlled environment where the users can interact with the product.

• Recording the users’ interactions with the product.

• Analyzing the results of the tests to identify areas of improvement.

• Making changes to the product based on the results.

Security testing is an important type of testing that is designed to identify and address security vulnerabilities in the software. The purpose of security testing is to ensure that the software is secure from potential threats and that it protects sensitive information and data from unauthorized access, manipulation, or theft.
The primary goal of security testing is to identify any security vulnerabilities or weaknesses in the software and to assess the software's ability to withstand potential attacks, such as hacking, phishing, or malware attacks. By identifying these vulnerabilities and weaknesses, security testing helps to mitigate potential security risks and protect the software and its users from potential harm.
In addition, security testing also helps to ensure compliance with industry standards and regulations, such as the Payment Card Industry Data Security Standard (PCI DSS), the Health Insurance Portability and Accountability Act (HIPAA), and the General Data Protection Regulation (GDPR). By adhering to these standards and regulations, organizations can maintain the trust of their customers and users and avoid costly penalties or legal action.
Overall, the purpose of security testing is to ensure that the software is secure, compliant, and protects sensitive information and data from potential security threats.

The most important part of the testing process is identifying the test cases that will provide the most comprehensive coverage of the system being tested. This involves understanding the system requirements and analyzing them to identify the various scenarios, conditions, and paths that must be tested. This often requires the use of various techniques such as boundary value analysis, equivalence partitioning, decision tables, and more.

For example, if a web application needs to be tested, the test cases should cover all the possible user actions on the application, such as clicking on various links, submitting forms, and other user interactions. Additionally, tests should be designed to cover edge cases and unexpected user inputs. Once all the test cases have been identified and designed, they should be executed and monitored to ensure they are providing the desired coverage.

Moreover, it is important to document the test cases in an organized way, so that they are easy to review and maintain. This helps to ensure that all the necessary tests are performed and that the quality of the tested product meets the required standards.

Test case design is a process of designing test cases for testing a software application to identify any gaps, errors, or missing requirements as compared to the actual requirements. There are three main techniques for test case design, which are Equivalence Partitioning, Boundary Value Analysis, and Error Guessing.

Equivalence Partitioning: This technique involves dividing input data into different equivalent classes, and then testing on a representative sample from each class. For example, if an input field requires the user to enter a number between 1 and 10, then the data can be divided into two equivalence classes - numbers below 1 and numbers above 10, and then a representative sample of each class can be tested.

Boundary Value Analysis: This technique involves testing the boundaries of an input value as well as values just outside the boundaries. For example, if an input field requires the user to enter a number between 1 and 10, then the boundaries should be tested with values of 1, 10, and 11.

Error Guessing: This technique involves the tester using their experience, knowledge, and intuition to identify potential errors and test them. For example, if the application is a calculator, the tester can test some commonly used calculations such as addition, subtraction, multiplication, and division.

In order to ensure that all the requirements of a system are tested, I would start by creating a detailed test plan that outlines the scope of the testing, the objectives and goals, and the applicable resources and timeline. I would then review the system design specifications and requirements to create test cases that cover each requirement. I would also create test data to cover different scenarios and ensure that I test the system with both valid and invalid data.

Additionally, I would review the test results to ensure that the system is meeting its requirements and making the necessary changes if needed.

For example, if I am testing an online payment system, I would first start by creating a test plan that covers the scope of the testing, the objectives and goals, and the timeline and resources. I would then review the system design specifications and requirements and create test cases that cover each requirement. I would also create test data to cover different scenarios, such as valid and invalid payments. I would also test the system with multiple payment methods, such as credit cards, PayPal, and Bitcoin. Additionally, I would review the test results to ensure that the system is meeting its requirements and making the necessary changes if needed.