These Software Testing multiple-choice questions and their answers will help you strengthen your grip on the subject of Software Testing. You can prepare for an upcoming exam or job interview with these Software Testing MCQs.
So scroll down and start answering.
A. Can stand up to development and fight for bugs to be fixed
B. all of the these
C. Can handle having 100 straight bugs marked as won't fix
D. Have been through full software development cycle
A. True
B. False
A. The tester wants to test all possible input data.
B. The tester has knowledge of the internal structures of the software.
C. The tester wants to reduce the total number of test cases that need to be developed.
D. The tester is unsure of all the input data sets.
A. Pilot Test involve Small group of end users but beta test involve large group
B. No difference
C. Beta Test involve small group of end users but Pilot Test involve large group
D. Difference are vague
A. Unexpected user input
B. Robustness of the software
C. Availability under a heavy load
D. Performance under a heavy load
A. partitions the tests between equal time spans
B. divides the test equally between the testers
C. divides the input data into partitions
D. tests whether disk partitions are equally distributed
A. running BVT and monitoring resources
B. running stress tests and monitoring resources
C. running code coverage and monitoring resources
A. Checking the changes and checking the side effects after the changes
B. Checking the changes
C. Checking the side effects after the changes
D. None
A. API testing
B. Statement coverage
C. Mutation testing
D. Boundary value analysis
A. True
B. False
A. False
B. True
A. Moderator, author/producer, reader
B. Author/producer, reader, inspector
C. Inspector, recorder
D. All of these
A. Only after the code was written
B. Testing teams don't plan the testing, the developers do
C. As early as possible
D. There is no need to plan, testing is done by the specs
A. Ad-hoc Testing
B. Unit Testing
C. Grey box Testing
D. Functional Testing
A. Tests a completely integrated system to verify that it meets its requirements
B. Tests that verify the functionality of a specific section of code
C. Assures that the system is installed correctly and working at actual customer's hardware
D. Tests that seeks to verify the interfaces between components against a software design
A. Whitebox testing
B. Beta testing
C. Performance testing
D. Equivalence Partitioning
A. Developer
B. Customer
C. Software Project Manager
D. Software Engineer
A. Use Case is part of the Test Planning
B. A Test Plan describes all the elements that make up the test strategy. It can include the application to be tested, the scope of the testing, the testing activities, roles and responsibilities and deliverables. A Use Case describes how the user interact
C. Test Plan is part of the Use Case
D. Test Plan and Use case are the same
A. Pass/Fail indicator
B. Related requirements
C. Related design decisions
D. Test case ID
A. Performance testing
B. Beta testing
C. Blackbox testing
D. Whitebox testing
A. Testing is typically performed by amateurs as a hobby and debugging is typically performed by professionals
B. Testing is the initial detecting of errors and debugging is the isolation and correction of errors
C. Testing and debugging are interchangeable terms and essentially the same activity
D. Debugging is a very cursory overview of the code and testing is a much more rigorous attempt at fixing the error
A. Functional testing includes test cases that validate security log ons, performance and testing of disk and memory space. Non-Functional testing includes the testing of the actual functions that the end user will be using, including transactions and repor
B. Non-functional testing includes test cases that validate security log ons, performance and testing of disk and memory space. Functional testing includes the testing of the actual functions that the end user will be using, including transactions and repor
A. White Box Testing
B. Security Testing
C. Usability Testing
D. Unit Testing
A. Unit testing is an action used to validate that separate units of source code remains working properly.
B. Checking that fixed bug do not affect the other sections of the modules by checking the functionality
A. 100000
B. depends
C. 300000
D. 200000
A. True
B. False
A. bug pool
B. test suite
C. scenario test
D. test compilation
A. PTQ
B. TPQ
C. CuteTP
D. QAT
E. QTP
A. Project manager's responsibility only.
B. Actions taken to avoid things that might negatively impact the scope, quality, timeliness or cost of the project.
C. Assessing the risk of not hiring enough testers for the project.
D. Analysis of how customers will react on software problems.
E. Marketing meeting where new features are discussed.
A. Only on new features; old features are already tested
B. Only where there is no testing team
C. Only on complex code; they should focus on developing
D. Always
A. Software Development Learning Center
B. Severe Defects Life Cycle
C. Software Development Life Cycle
D. Software Defects Life Cycle
E. Software Detection Life Cycle
A. True
B. False
A. Black box
B. White box
C. Red box
D. Gray box
A. all of the these
B. II. great at managing business requirements
C. I. great at specs and schedules
D. III. both a tester and a program manager
A. Table of content followed by multiple characters.
B. Developed by business analysts to meet the requirements.
C. Collective work of QA team on software testing risks.
D. Document that describes the objectives, scope, approach and focus of software testing effort.
A. busy variation testing
B. build validation topic
C. bane of my very existence
D. build verification tests
A. Blackbox testing
B. Whitebox testing
C. Unit testing
D. Beta testing
A. True
B. False
A. QTP
B. Soap UI
C. Selenium
D. Sahi
E. Load Runner
A. False
B. TRUE
A. Code Review
B. Test Case
C. Specification
D. Test Step
A. Test Studio
B. Drupal
C. Selenium
D. QTP
A. Configuration testing
B. Performance testing
C. Blackbox testing
D. Stress testing
A. It may be difficult to determine of the test has passed or failed
B. We cannot automate the user inputs
C. It may be difficult to repeat the test
D. It is not possible to run the test
A. No difference, they are the same thing
B. Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects
C. Regression testing ensures the original fault has been removed; Re-testing looks for unexpected side-effects
A. This testing refers to the practice of moving and testing an application on different platforms
B. This refers to testing the applications in different servers
C. This refers to testing the applications in different browsers
A. Waterfall model
B. V-model
C. Spiral model
D. Agile Development
A. Software Quality Assurance
B. Test planning
C. Risk reduction
D. Testing
A. True
B. False
A. Completed Path Analysis
B. Completed Test incident Report
C. Completed Code Coverage Analysis
D. Completed Requirements traceability matrix
E. Completed Test Summary Report