Home/general interview questions/Page 12
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the various software testing levels?
Unit testing Among the software testing levels, unit testing is the lowest level. The software's modules or applications are referred to as units. The programmer who tests the modules also performs unit testing, and immediately fixes any discovered bugs. Integration testing All of the tested componeRead more
Unit testing
Among the software testing levels, unit testing is the lowest level. The software’s modules or applications are referred to as units. The programmer who tests the modules also performs unit testing, and immediately fixes any discovered bugs.
Integration testing
All of the tested components are combined to form integration, and they are all tested collectively. Data that moves from one module to another is tested as part of integration testing. In essence, it examines the interaction between two or more modules, but not their functionality alone.
System testing
System testing tests the complete or integrated system. It evaluates the software to ensure it complies with standards outlined in the SRS guideline. It conducts both functional and non-functional testing and is the last test.
Acceptance testing
Customers or users conduct acceptance testing to determine whether the product satisfies their needs.
See lessWhat distinguishes exploratory testing from adhoc testing?
Adhoc testing Adhoc testing is a non-formal process of testing software without any planning, requirements, specifications, or documentation. Its fundamental purpose is to attain perfection in testing. Most entry-level professionals can conduct adhoc testing — you don’t need an experienced testing eRead more
Adhoc testing
Adhoc testing is a non-formal process of testing software without any planning, requirements, specifications, or documentation. Its fundamental purpose is to attain perfection in testing. Most entry-level professionals can conduct adhoc testing — you don’t need an experienced testing engineer.
Exploratory testing
Exploratory testing requires documentation and proper planning. It entails simultaneous learning, test design, and test execution. A methodical strategy, exploratory testing’s primary goal is to become familiar with the application. Similar to adhoc testing, exploratory testing does not require an experienced testing engineer.
See lessHow do you know when enough tests have been administered?
This is one of the most important QA testing interview questions. Sometimes, as a project manager or project lead, we may have to cancel testing to launch the product quicker. In those circumstances, we must determine whether the product has received sufficient testing from testers. We’d consider: IRead more
This is one of the most important QA testing interview questions. Sometimes, as a project manager or project lead, we may have to cancel testing to launch the product quicker. In those circumstances, we must determine whether the product has received sufficient testing from testers.
We’d consider:
- If the testing or release deadlines are met.
- If the risk in the real-time project is below the permitted level.
- If all the critical bugs and roadblocks have been resolved.
- If our submission meets the requirements.
See lessHow are test cases created?
There are two methods for creating test cases: Black box testing The testers consider the software as a black box with inputs and outputs in this specification-based testing method. In "black box" testing, the testers are unaware of the internal workings of the software; instead, they are only awareRead more
There are two methods for creating test cases:
Black box testing
The testers consider the software as a black box with inputs and outputs in this specification-based testing method. In “black box” testing, the testers are unaware of the internal workings of the software; instead, they are only aware of the functions it performs. This kind of testing methodology is acceptable for all testing levels when the specification is present.
White box testing
White box testing assesses the logic and internal organization of the code. The testers must possess coding skills in order to implement white box testing so that they can work with internal code. They investigate the code and identify the problematic unit.
See lessWhat is a test plan?
The test plan document is a document that details how all testing procedures will be carried out in order to deliver a high-quality product. It is the result of a number of processes, including the creation of product descriptions, SRSs, or Use Case documentation for all upcoming project tasks. A teRead more
The test plan document is a document that details how all testing procedures will be carried out in order to deliver a high-quality product. It is the result of a number of processes, including the creation of product descriptions, SRSs, or Use Case documentation for all upcoming project tasks. A test manager or test lead is often responsible for creating a test plan, and its main purpose is to outline who will conduct which tests and when, as well as what needs to be tested.
See lessWhat does a quality audit mean?
A processor quality system's on-site verification process, such as an inspection or examination, is referred to as an audit. Quality auditing is the systematic examination of a quality system by a team of auditors, either internal or external. To ensure that the organization has clearly defined inteRead more
A processor quality system’s on-site verification process, such as an inspection or examination, is referred to as an audit. Quality auditing is the systematic examination of a quality system by a team of auditors, either internal or external.
To ensure that the organization has clearly defined internal system monitoring procedures linked to effective action, quality audits are carried out at preset intervals. A crucial management technique for confirming objective proof of procedures is the audit.
See lessWhat distinguishes preventive from reactive approaches?
Preventive Approach: This is a strategy used to avoid problems, also known as the verification process. Tests are created early in the software development lifecycle, prior to the software even being created. This strategy falls under the category of quality analysis, where testers attempt to stop fRead more
Preventive Approach: This is a strategy used to avoid problems, also known as the verification process. Tests are created early in the software development lifecycle, prior to the software even being created. This strategy falls under the category of quality analysis, where testers attempt to stop faults in their tracks.
Reactive Strategy: Also referred to as the validation process, a reactive strategy is meant to find (or react) to flaws. The tests in this method are created to run after the software development, and it’s governed by Quality Control.
See lessWhat is monkey testing?
Monkey testing is a type of black box testing that assesses an application by supplying random inputs to check the system's behavior (i.e., whether it crashes). When a user gives random inputs to test the system's behavior, this type of testing takes place automatically. Monkey testing doesn’t requiRead more
Monkey testing is a type of black box testing that assesses an application by supplying random inputs to check the system’s behavior (i.e., whether it crashes). When a user gives random inputs to test the system’s behavior, this type of testing takes place automatically.
Monkey testing doesn’t require test cases. It can also be automated, meaning we can create scripts or programs to generate random inputs to monitor how the system behaves. When conducting stress or load testing, this method is helpful.
Two varieties of monkeys exist: smart monkeys and dumb monkeys.
Smart Monkeys
Dumb Monkeys
- Dumb monkeys have no knowledge about the application.
- They are unaware of the pages to which an application will redirect.
- They supply arbitrary inputs and are unaware of the application’s beginning and end.
- Despite their lack of application knowledge, they still discover issues like hardware or environmental failure.
- They also have limited knowledge of an application’s UI and functionality.
See lessWhat are the risk dimensions in QA?
The risk dimensions in QA are as follows: Timetables: Unrealistic timetables for developing a large piece of software in a single day. Client: Uncertain requirements, unclear requirements, and changing requirements. Human Resource: Lack of adequate human resources with the required level of expertisRead more
The risk dimensions in QA are as follows:
- Timetables: Unrealistic timetables for developing a large piece of software in a single day.
- Client: Uncertain requirements, unclear requirements, and changing requirements.
- Human Resource: Lack of adequate human resources with the required level of expertise in the project.
- System Resources: Failure to acquire all necessary resources, including hardware and software tools or software licenses, will have a negative impact.
- Quality: Various circumstances, such as a shortage of resources, a strict delivery timetable, and frequent modifications to the requirement, significantly impact the quality of the application under test (AUT).
See lessWhat is the QA team's role in software development?
By keeping an eye on the entire development process, the QA team assures the quality. QA monitors results and modifies procedures as necessary to fulfill expectations. The role of quality control includes: Keeping an eye on the ongoing development process. Planning, testing, and process execution. GRead more
By keeping an eye on the entire development process, the QA team assures the quality. QA monitors results and modifies procedures as necessary to fulfill expectations.
The role of quality control includes:
- Keeping an eye on the ongoing development process.
- Planning, testing, and process execution.
- Guarantees that test cases can be traced back to the requirements
See less