Home/qa interview questions/Page 2
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 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 lessDifferentiate between verification and validation.
Verification Verification assesses development-phase procedures to see if they adhere to user requirements. For example, static testing is verification. Before validation, verification testing is carried out. It is not related to running the code. It entails tasks including desk checks, walkthroughsRead more
Verification
Verification assesses development-phase procedures to see if they adhere to user requirements. For example, static testing is verification. Before validation, verification testing is carried out. It is not related to running the code. It entails tasks including desk checks, walkthroughs, inspections, and reviews. Before the development cycle, the bugs are discovered. It complies with the standards outlined in the SRS paper.
The QA team provides verification, ensuring that the program complies with the specifications as down in the SRS document.
Validation
Validation evaluates the product to ensure it satisfies requirements after the development phase, and after verification.
It uses techniques like non-functional testing, white box testing, and black box testing. The bugs are discovered after the development cycle. It determines whether or not it satisfies the requirements.
See lessWhat is a matrix of traceability?
A traceability matrix is a document that links test cases with user requirements. Its primary goal is to ensure that all test cases are included and no functionality is overlooked while conducting software testing.
A traceability matrix is a document that links test cases with user requirements. Its primary goal is to ensure that all test cases are included and no functionality is overlooked while conducting software testing.
See lessDescribe MR and the information it contains.
Modification Request, often known as a defect report, is referred to as MR. It’s meant to report software defects, issues, and ideas.
Modification Request, often known as a defect report, is referred to as MR. It’s meant to report software defects, issues, and ideas.
See lessWhat information should your QA documentation contain?
QA testing documentation must have: Listed flaws found prioritized based on severity. Descriptions for each demand or business function. Inspection reports Configurations Test strategy and test case Bug reports User guides Distinct reports for management and users
QA testing documentation must have:
- Listed flaws found prioritized based on severity.
- Descriptions for each demand or business function.
- Inspection reports
- Configurations
- Test strategy and test case
- Bug reports
- User guides
- Distinct reports for management and users
See lessWhat are the types of documents in SQA?
Here are the various types of documents in SQA: Requirement document Test Metrics Transaction mix Test log Test incident report Test summary report User profiles Test cases and test plan Task distribution flow chart
Here are the various types of documents in SQA:
- Requirement document
- Test Metrics
- Transaction mix
- Test log
- Test incident report
- Test summary report
- User profiles
- Test cases and test plan
- Task distribution flow chart
See less