What is adhoc testing?
Adhoc testing is an informal way of testing the software. It does not follow the formal process like requirement documents, test plan, test cases, etc.
Characteristics of adhoc testing are:
- Adhoc testing is performed after the completion of formal testing on an application.
- The main aim of adhoc testing is to break the application without following any process.
- The testers who are executing the adhoc testing should have a deep knowledge of a product.
Write the differences between Preventive and Reactive approaches?
Preventive Approach: It is also known as the Verification process. Preventive is the approach to prevent defects. In this approach, tests are designed in its early stages of Software Development Lifecycle before the software has developed. In this approach, testers try to prevent defects in the early stages; it comes under Quality Analysis.
Reactive Approach: It is also known as Validation Process. This approach is to identify defects. In this approach, tests are designed to execute after the software’s development. In this approach, we try to find out the defects. It comes under Quality Control.
What is Quality Assurance?
QA stands Quality Assurance. QA is a set of activities designed to ensure that the developed software meets all the specifications or requirements mentioned in the SRS document.
QA follows the :
Plan
The plan is a phase in Quality Assurance in which the organization determines the processes which are required to build a high-quality software product.
Do
Do is a phase of development and testing the processes.
Check
This phase is used for monitoring the processes and verifies whether these processes meet the user requirements or not.
Act
The Act is a phase for implementing the actions required to improve the processes.
What is traceability matrix?
Traceability matrix is a document that maps and traces user requirements with test cases. The main aim of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality miss during the software testing.
How is monkey testing different from adhoc testing?
Both monkey testing and adhoc testing follows the informal approach, but in monkey testing, we do not need to have deep knowledge of the software. However, to perform adhoc testing, testers should have a deep knowledge of the software.
What is the Quality Audit?
An Audit is defined as on-site verification activity, such as inspection or examination, of a processor quality system. Quality Audit is the process of systematic analysis of a quality system carried out by an internal or external quality auditor, or an audit team. Quality Audits are performed at predefined time intervals and ensure that the institution has clearly defined internal system monitoring procedures linked to effective action. Audits are an essential management tool to be used for verifying objective evidence of processes.
How the build and release differ from one another, write down the difference between build and release?
Build is defined as when the software is given to the testing team by the development team.
Release It is defined as when the software is handed over to the users by the tester and developer.
What are the different levels in software testing?
There are four different levels in software testing:
- Unit/Component testing
- Integration testing
- System testing
- Acceptance testing
Unit testing - It is the lowest level in most of the models.
- Units are the programs or modules in the software.
Unit testing is performed by the programmer that tests the modules, and if any bug is found, then it is fixed instantaneously.
Integration testing
- Integration means the combination of all the modules, and all these modules are tested as a group.
- Integration testing performs the testing on the data that flows from one module to another module.
- It basically checks the communication between two or more modules but not the functionality of individual modules.
System testing
- System testing is used to test the complete or integrated system.
- It tests the software to ensure that it conforms the specified requirements specified in the SRS document.
- It is the final test and performs both functional and non-functional testing.
Acceptance testing - Acceptance testing is performed by the users or customers to check whether it meets their requirements or not.
What is a test plan?
The Test Plan document is a document which contains the plan for all the testing activities to deliver a quality product. The test Plan document is derived from many activities such as product description, SRS, or Use Case documents for all future events of the project. The Test Lead usually prepares it, or Test manager and the focus of the document is to describe what to test, how to test when to test, who will do what test.
Define bug leakage and bug release?
Bug leakage is defined as the bug not found by the testing team but found by the end users. Bug release it is defined when the software is released by the tester in the market knowing that bug is present in the release. These types of bugs have low priority and severity. This type of situation arises when customers want the software on time than the delay in getting the software and the cost involved in correcting the bugs.