CSTE Software Testing Certification Exam Question Pattern

This tutorial will give you a general idea of the CSTE Certification exam paper pattern.

We have included some sample questions and answers for the CSTE mock test paper. You can refer to these questions and can judge the pattern of the descriptive answer paper.

If you need objective type questions from the CSTE paper, you can refer to our previous tutorial on CSTE objective type question answers. You can also download some more sample papers from our ‘Downloads’ section.

Let’s move on!!


CSTE Mock Test Paper – Questions and Answers

Q #1) Define the following along with examples [25 Marks]

a. Boundary Value testing
b. Equivalence testing
c. Error Guessing
d. Desk checking
e. Control Flow analysis


a) Boundary Value Analysis: This process involves selecting test cases/data by identifying the boundaries that separate valid and invalid conditions.

Tests are constructed to test the inside and outside edges of these boundaries, in addition to the actual boundary points or A selection technique in which test data are chosen to lie along “boundaries” of the input domain [or output range] classes, data structures, procedure parameters, etc.

Choices often include maximum, minimum, and trivial values or parameters.

For example, Input data 1 to 10 (boundary value)
Test input data 0, 1, 2 to 9, 10, 11

b) Equivalence Testing: The input domain of the system is partitioned into classes of representative values so that the number of test cases can be limited to one-per-class, which represents the minimum number of test cases that must be executed.

For Example, valid data range: 1-10
Test set:-2; 5; 14

c) Error Guessing: Test data selection technique. The selection criterion is to pick values that seem likely to cause errors. Error Guessing is based mostly upon experience, with some assistance from other techniques such as Boundary Value Analysis.

Based on experience, the test designer guesses the types of errors that could occur in a particular type of software and designs the test cases to uncover them.

For example, if any type of resource is allocated dynamically, then a good place to look for errors is in the de-allocation of resources. Are all resources correctly deallocated, or are some lost as the software executes?

d) Desk Checking: Desk Checking is conducted by the developer of the system or program. The process involves reviewing the complete product to ensure that it is structurally sound and the standards and requirements have been met. This is the most traditional means for analyzing a system or program.

e) Control Flow Analysis: It is based upon the graphical representation of the program process. In Control Flow Analysis; the program graphs have nodes that represent a statement or segment possibly ending in an unresolved branch.

The graph illustrates the flow of program control from one segment to another as illustrated through branches. The objective of the Control Flow Analysis is to determine the potential problems in logic branches that might result in a loop condition or improper processing.

Q #2) You find that there is a senior tester who is making more mistakes than the junior testers. You need to communicate this aspect to the senior tester. Also, you don’t want to lose this tester. How should one go about constructive criticism? [10 Marks]

Answer: In the quality approach, it is the responsibility of the supervisor to make his/her subordinates successful. The effective use of criticism is a tool for improving subordinate performance.

While providing constructive criticism, you should incorporate the following tactics:

  • Do it privately.
  • Have the facts.
  • Be prepared to help the worker improve his/her performance.
  • Be specific about Expectations.
  • Follow a specific process in giving criticism.

Q #3) Your manager has taken you on board as a test lead for testing a Web-based Application. He wants to know what risks you would include in the Test Plan. Explain each risk factor that would be a part of your test plan. [20 marks]


Given below are the Primary Risk Factors of a Web-Based Application:

  • Security: Anything related to the security of the application.
  • Performance: The number of computing resources and code required by the system to perform its stated functions.
  • Correctness: Data entered, processed, and outputted in the system is accurate and complete.
  • Access Control: Assurance that the application system resources will be protected.
  • Continuity of processing: The ability to sustain processing in the event a problem occurs.
  • Audit Trail: The capability to substantiate the process that has occurred.
  • Authorization: Assurance that the data is processed in accordance with the intent of the management.

General/Secondary Risks:

  • Complex: Anything disproportionately large, intricate or convoluted.
  • New: Anything that has no history in the product.
  • Changed: Anything that has been tampered with or “improved”.
  • Upstream Dependency: Anything whose failure will cause cascading failure in the rest of the system.
  • Downstream Dependency: Anything that is especially sensitive to failures in the rest of the system.
  • Critical: Anything whose failure could cause substantial damage.
  • Precise: Anything that must meet its requirements exactly.
  • Popular: Anything that will be used a lot.
  • Strategic: Anything that has special importance to your business, such as a feature that sets you apart from the competition.
  • Third-party: Anything used in the product, but developed outside the project.
  • Distributed: Anything spread out in time or space, yet whose elements must work together.
  • Buggy: Anything known to have a lot of problems.
  • Recent Failure: Anything with a recent history of failure.

Q #4) You are in the contract stage of a project and are developing a comprehensive proposal for a safety-critical software system. Your director has consulted you to prepare a guideline document that will enlist the user’s role during the Acceptance Testing phase.

Indicate the key roles you feel the user should play during the acceptance stage. Also, indicate the categories into which the acceptance requirements should fall. [10 Marks]


  • Ensure user involvement in developing system requirements and acceptance criteria.
  • Identify interim and final products for acceptance of their acceptance criteria and schedule.
  • Plan how and by whom each acceptance activity will be performed.
  • Plan resources to provide information.
  • Schedule adequate time for buyer staff to receive & examine products and evaluation prior to acceptance review.
  • Prepare an acceptance plan.
  • Respond to the analysis of project entitlements before accepting and rejecting.
  • Approve the various interim software products.
  • Perform final acceptance activities, including formal acceptance testing at delivery.
  • Make an acceptance decision for each product.

Q #5) What is Parallel Testing and when do we use Parallel Testing? Explain this with a simple example. [5 marks]

Answer: Testing a new or altered data processing system with the same source data that is used in another system is Parallel Testing. The other system is considered as the standard of comparison. OR we can say that parallel testing requires the same input data to be run through two versions of the same application.

Parallel testing should be used when there is uncertainty regarding the correctness of the processing of the new application. Old and new versions of the applications are the same.

For Example,

  • Operate old and new versions of the payroll system to determine if paychecks from both the systems are reconcilable.
  • Run the old version of the application system to ensure that the operational status of the old system has been maintained in the event that the problems are encountered in the new application.

Q #6) What is the difference between testing Techniques and Tools? Give examples. [5 marks]


Testing Technique: This is a process for ensuring that some aspects of the application system or unit function properly, and there may be few techniques but many tools.

Tools: It is a vehicle for performing a test process. The tool is a resource for the tester, but itself is insufficient to conduct testing

For Example, The swinging of a hammer to drive the nail. A hammer is a tool, and swinging the hammer is a technique. The concept of tools and technique is important in the testing process. It is a combination of the two that enables the test process to be performed.

The tester should first understand the testing techniques and then understand the tools that can be used with each of the techniques.

Q #7) Quality control activities are focused on identifying defects in the actual products produced. However, your boss wants you to identify and define processes that would prevent defects. How would you explain to him to distinguish between QA and QC responsibilities? [10 Marks]


Quality Assurance:

  • A planned and systematic set of activities necessary to provide adequate confidence that the requirements are properly established and products/services conform to the specified requirements
  • An activity that establishes and evaluates the processes to produce the products.
  • Helps to establish processes.
  • Sets up measurement programs to evaluate processes.
  • Identify weaknesses in processes and improve them.
  • QA is the responsibility of the entire team.
  • Prevents the introduction of issues or defects.

Quality Control:

  • The process by which the product quality is compared with applicable standards; and the action is taken when non-conformance is detected.
  • An activity that verifies if the product meets pre-defined standards.
  • Implement the process.
  • Verify if a specific attribute(s) is in a specific product or service
  • Identifies defects for the primary purpose of correcting defects.
  • QC is the responsibility of the tester.
  • Detects, reports and corrects defects.

Q #8 ) Differentiate between Transaction Flow Modeling, Finite State Modeling, Data Flow Modeling and Timing Modeling. [10 Marks]


Transaction Flow Modeling: The nodes represent the steps in transactions. The links represent the logical connection between the steps.

Finite State Modeling: The nodes represent different user observable states of the software. The links represent the transitions that occur when moving from state to state.

Data Flow Modeling: The nodes represent the data objects. The links represent the transformations that occur when translating one data object to another.

Timing Modeling: The nodes are Program Objects. The links are sequential connections between the program objects. The link weights are used to specify the required execution time as the program executes.

9) According to you, what are the two primary goals of Testing? [5 Marks]


  • Determine whether the system meets specifications (producer view)
  • Determine whether the system meets business and user needs (Customer view)

Hope this tutorial helped you to get an idea of the CSTE Software Testing Certification Exam Question Pattern. Let us know your feedback in the comments section below!

Related Post

Leave a Reply

Your email address will not be published.