Manual Testing Assessment Test

Reviewed by Editorial Team

The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.

Learn about Our Editorial Process

| By Cripstwick

Cripstwick

Community Contributor

Quizzes Created: 636 | Total Attempts: 823,595

| Attempts: 212

Questions

Feedback

During the Quiz End of Quiz

Difficulty

Easy First Hard First Sequential

Share on Facebook Share on Twitter Share on Whatsapp Share on Pinterest Share on Email Copy to Clipboard Embed on your website

1/10 Questions

Another name for acceptance testing is
- Beta Testing
- Grey Box Testing
- Functional Testing
- Adhoc Testing

About This Quiz

Manual Testing is a process that has to do with locating bugs or defects in a software program. Are you a pro at Manual Testing? Do you want a challenge or wish to learn more? Take our quiz to challenge yourself today!

2.

Which of the following is a testing level?
- Unit Testing
- Objectives
- Base Testing
- All Of The Above
Correct Answer

A. Unit Testing

Explanation

Unit testing is a testing level that involves testing individual units or components of a software system to ensure that they function correctly. It focuses on verifying the smallest testable parts of the system in isolation. Objectives and base testing are not specific testing levels, but rather general terms that can apply to testing at any level. Therefore, the correct answer is Unit Testing.

Rate this question:
3.

Incidents would not be raised against one of these
- Documentation
- Requirements
- Suggested Improvements
- Test Cases
Correct Answer

A. Suggested Improvements

Explanation

This answer is correct because incidents are typically raised against documentation, requirements, and test cases when there are issues or problems identified. However, suggested improvements are not typically the subject of incidents as they are recommendations for making enhancements or optimizations rather than addressing identified problems. Therefore, incidents would not be raised against suggested improvements.

Rate this question:
4.

How Possible is Exhaustive Testing?
- It is always possible
- It is Practically Possible
- It is Impractical but Possible
- It Is Impractical and Impossible
Correct Answer

A. It is Impractical but Possible

Explanation

Exhaustive testing refers to testing every possible combination and scenario of a system, which is practically impossible due to the large number of inputs and interactions. Therefore, it is considered impractical. However, in theory, it is still possible to perform exhaustive testing if time and resources are unlimited.

Rate this question:
5.

Which of these techniques is not a whitebox technique?
- Condition Coverage
- Boundary Value Analysis
- Decision Testing and Coverage
- Statement Testing and Coverage
Correct Answer

A. Boundary Value Analysis

Explanation

Boundary Value Analysis is not a whitebox technique because it focuses on testing the input and output values at the boundaries of the input domain, without considering the internal structure or implementation details of the system. Whitebox techniques, on the other hand, involve examining the internal structure and logic of the system, such as condition coverage, decision testing, and statement testing.

Rate this question:
6.

Which of the following best describes static analysis?
- Use of Black Box Testing
- Analysis of Program Code
- Reviewing of Test Plans
- Analysis of Batch Programs
Correct Answer

A. Analysis of Program Code

Explanation

Static analysis refers to the process of analyzing program code without actually executing it. It involves examining the code for potential errors, vulnerabilities, or quality issues. This analysis helps in identifying bugs, security flaws, and coding standards violations before the code is executed. It is an essential part of the software development life cycle as it helps in improving the overall quality and reliability of the software. Therefore, "Analysis of Program Code" is the best description of static analysis.

Rate this question:
7.

What phase is the handover of test ware part of?
- Evaluating Exit Criteria and Reporting
- Test Analysis and Design
- Test Planning and Control
- Test Closure Activities
Correct Answer

A. Test Closure Activities

Explanation

The handover of test ware is part of the Test Closure Activities phase. This phase involves completing and archiving all test deliverables, such as test scripts, test data, and test reports. It also includes conducting a final review of the project and documenting lessons learned. The handover of test ware is an important step in closing out the testing process and ensuring that all necessary documentation and artifacts are properly transferred and stored.

Rate this question:
8.

Who documents all the issues, problems and open points that were identified during a formal review?
- Moderator
- Scribe
- Author
- Manager
Correct Answer

A. Scribe

Explanation

A scribe is responsible for documenting all the issues, problems, and open points that were identified during a formal review. This role involves taking detailed notes and recording all the discussions and decisions made during the review process. The scribe ensures that all the information is accurately documented for future reference and follow-up actions. They play a crucial role in capturing and organizing the outcomes of the review, providing a comprehensive record of the identified issues and points that need to be addressed.

Rate this question:
9.

What is Verification based on?
- Input Based
- Storage Based
- Product Based
- Process Based
Correct Answer

A. Process Based

Explanation

Verification is a process in which the correctness of a system or component is evaluated. It involves reviewing, inspecting, testing, and analyzing the system or component to ensure that it meets the specified requirements. Therefore, verification is based on the process, as it focuses on evaluating the steps and activities involved in the development of the system or component to ensure its correctness.

Rate this question:
10.

Whitebox testing is also called?
- Clear Box Testing
- Open Box Testing
- Clear Box Testing
- Glass Box Testing
Correct Answer

A. Clear Box Testing

Explanation

Whitebox testing is a software testing technique where the internal structure, design, and implementation of the system being tested are known to the tester. It is also known as clear box testing or glass box testing because the tester has clear visibility into the system being tested. The tester can examine the code, logic, and algorithms to design test cases that cover all possible paths and scenarios. This type of testing is useful in identifying errors, loopholes, and vulnerabilities in the system.

Rate this question: