Home/qa interview questions/Page 3
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.
List out software quality steps through the software development cycle.
Review the requirements before starting the development phase. Review the code. Write comprehensive test cases. Session-based testing. Risk-based testing. Prioritize bugs based on usage. Form dedicated security and performance testing team. Run a regression cycle. Perform sanity tests on production.Read more
- Review the requirements before starting the development phase.
- Review the code.
- Write comprehensive test cases.
- Session-based testing.
- Risk-based testing.
- Prioritize bugs based on usage.
- Form dedicated security and performance testing team.
- Run a regression cycle.
- Perform sanity tests on production.
- Simulate customer accounts on production.
- Include software QA Test Reports.
See lessDescribe the distinction between retesting and regression testing.
Regression Regression testing is a type of analysis used to determine whether recent code changes have had an impact on previously unaffected features. Regression testing's primary goal is to ensure any code modifications cannot negatively affect functionalities already in place. General testing; itRead more
Regression
Retesting
- Retesting entails testing modules that were unsuccessful during the previous run.
- Retesting is performing testing on already corrected flaws.
- Planned; not spontaneous.
- Cannot be automated
- Includes defect verification.
- Always performed after retesting because retesting has a higher priority.
See lessWhat is a software testing test metric, and what data does it contain?
The term "Test Metric'' refers to the accepted practices for testing software. These data describe the format or substance of an exam. It includes details such as total tests run, tests passed, tests failed, tests deferred, and tests that were successfully completed the first time.
The term “Test Metric” refers to the accepted practices for testing software. These data describe the format or substance of an exam. It includes details such as total tests run, tests passed, tests failed, tests deferred, and tests that were successfully completed the first time.
See lessWhat is a cause-and-effect diagram?
A cause-and-effect diagram is a visual depiction of inputs and the effects they have on corresponding outputs, and it can be used to create test cases.
A cause-and-effect diagram is a visual depiction of inputs and the effects they have on corresponding outputs, and it can be used to create test cases.
See lessExplain what bug triage is.
Bug triage reviews bugs to make sure that they are valid, reproducible, and hold accurate information needed to resolve those bugs. Once you triage bugs, they’re scheduled for testing based on priority.
Bug triage reviews bugs to make sure that they are valid, reproducible, and hold accurate information needed to resolve those bugs. Once you triage bugs, they’re scheduled for testing based on priority.
See lessList out the roles of the Software Quality Assurance engineer.
A software quality assurance engineer has the following duties: Writing source code Software design Control of source code Reviewing code Change management Configuration management Integration of software Program testing Release management process
A software quality assurance engineer has the following duties:
- Writing source code
- Software design
- Control of source code
- Reviewing code
- Change management
- Configuration management
- Integration of software
- Program testing
- Release management process
See lessWhat are a test driver and a test stub, and why are they necessary?
The stub is the software component that needs to be tested. It is employed in a top-down manner. The component being tested is called by the driver. It is utilized in a bottom-up strategy. When only module X has been developed, and we need to test the interface between modules X and Y, it is necessaRead more
The stub is the software component that needs to be tested. It is employed in a top-down manner.
The component being tested is called by the driver. It is utilized in a bottom-up strategy.
When only module X has been developed, and we need to test the interface between modules X and Y, it is necessary. Therefore, we cannot just test module X; however, if there is a dummy module, we can use it to test module X.
See lessWhat is ad-hoc testing?
In ad-hoc testing, the tester randomly tests the system's functioning in an effort to break it. It is unstructured testing that takes place without any planning and documentation. As a result, it does not involve any test case preparation, test execution strategy, and requirement specification. Ad hRead more
In ad-hoc testing, the tester randomly tests the system’s functioning in an effort to break it. It is unstructured testing that takes place without any planning and documentation. As a result, it does not involve any test case preparation, test execution strategy, and requirement specification.
Ad hoc testing has the following traits:
- It takes place after formal testing concludes.
- Its primary goal is to malfunction the program without using a predetermined procedure.
- Ad hoc testers should be knowledgeable about the product they are testing.
See lessWhat is configuration management?
Configuration management describes the documentation of any modifications made to a project. Release control, change control, and revision control are the most important configuration management components.
Configuration management describes the documentation of any modifications made to a project. Release control, change control, and revision control are the most important configuration management components.
See lessWhat is thread testing?
Thread testing validates the critical functional capabilities of a specific task called a thread. The testing team performs thread testing at the onset of integration testing.
Thread testing validates the critical functional capabilities of a specific task called a thread. The testing team performs thread testing at the onset of integration testing.
See less