Recent Posts

QTP & Keyword Driven Testing

Tricky Questions in QTP

Asset Upgrade tool in QTP

New Features in QTP 10

Nov 18, 2008

Preparation for CSTE (Certified Software Test Engineer) Exam

Subscribe the QA and Software Testing Newsletter
Post Your Queries | QA and Testing - Table of Contents

SPONSORED LINKS Reading: Preparation for CSTE (Certified Software Test Engineer) ExamTweet this Post

Guidelines to Answer Questions
The examination proctor will give you one part of the examination at a time. As you receive each part, use the following steps to answer the questions:
1. Read the entire examination part before answering any questions.
�� For multiple-choice parts, only read each question’s stem, not the four to five
responses.
�� For essay parts, read all of the essay questions thoroughly.

2. As you read through each question (multiple-choice and essay) determine whether:
�� You absolutely know the answer to this question.
�� You believe you know the answer to this question.
�� You are not sure you know the answer, or it would take time to develop an
answer.

3. For both multiple-choice and essay questions, answer the questions that you know the answers; they should not take you much time to complete. This will give you the
majority of the examination time for the other questions you may need more time to
answer.

4. Answer the questions that you believe you know the answer.
�� For multiple-choice questions, answer all of the questions.

�� For essay questions, answer the questions worth the most points first, followed by
those worth less points. Note that the points equal the percentage of score allocated
to that essay question.

5. Answer the questions that you do not know the answer.
�� For multiple-choice questions, answer all of the questions.
�� For essay questions, answer the questions worth the most points first, followed by
those worth less points.
Follow these recommended guidelines for answering essay questions. Remember that an individual grades your examination. Make your thoughts and ideas clear and concise. Also, be sure to write legibly.

�� Those questions worth the most points should be the longest essay response. For example, if an essay question is worth 25 points, the response should be at least twice as long as an essay response for a question worth 10 points.

�� You need not write complete sentences. Those grading your examination are looking for key phrases and concepts. You can highlight them in a bulleted form, underlined or capitalized. This will help ensure that the individual scoring your examination can readily understand your knowledge of the correct response to that essay question.

�� Charts, graphs, and examples enhance your responses and enable the individual grading your examination to evaluate your understanding of the question. For example, use a control chart example to clearly indicate your knowledge of statistical process control.

Follow these recommended guidelines for answering multiple-choice questions.

�� Each multiple-choice question is comprised of a stem statement (or stem) and multiple responses to the stem. Read the stem carefully to assure you understand what is being asked. Then without reading the given responses to the stem, create in your mind what you believe would be the correct response. Look for that response in the list of responses.
�� You will be given four or five responses to each stem.
�� If you cannot create a response to the stem prior to reading the responses, attempt to eliminate those responses which are obviously wrong. In most cases, after that you will only have two responses remaining.
�� To select between what appears to be correct responses, rethink the subject matter in the stem and document what you know about that subject. This type of analysis should help you to eliminate a response or select the correct response among what should be two responses.

Follow these recommended guidelines when you do not know the answer to a question. Usually you can take a few minutes to look over the choices or write down some key points to help you answer the questions.

�� For multiple-choice questions, answer all questions – there is no reduction to your score for wrong answers. If you do not know the answer, try to rule out some of the potential responses. Then select the response you believe might be correct.



The Introduction of this preparation guide explained a process for you to follow to prepare for the examination. It emphasized familiarizing yourself with a Common Body of Knowledge (CBOK), the vocabulary of software quality, the activities performed by testing professionals, and reviewing several other different references that are included on the software certifications Web site. Other references you might look at include articles in professional IT publications.

If you feel you are ready to take the examination, you need to schedule the examination. Be sure to visit www.softwarecertifications.org for up-to-date CSTE examination dates and places. Once scheduled, the remaining event is to take the examination.


The Certified Software Test Engineer Exam is largely focused on the following areas:

General:
* Knowledge of the Test Environment.

* Ability to plan tests.

* Ability to execute tests, design test cases, use test tools etc.

* Ability to develop testing status reports.

Test Principles and Concepts: Definition of Test Specifications, Testing Techniques, Testing Methods, Independent Testing, Commercial off the Shelf (COTS) Software, Testing Code Developed Under Outside Contract, Test Quality, Testing Life Cycle & Technical Terms used in Testing. Role of Software Testers in Software Development:

* Software Development and Acquisition Process: Process Knowledge – Knowledge on Software Development, Operation, and Maintenance Process, Tools, Project Management, Test Documentation and Roles & Responsibilities.

* Test Approaches: Structural Test Approaches & Functional Test Approaches.

* "V" Testing Concept

* Quality Attributes.

Test Management:

* Test Management: Test Objectives, Test Competency, Test Performance, Test Technology, Staffing & Management of Staff.

* Giving Information: Audience Evaluation, Effective Presentation, Written Correspondence and Oral Delivery.

* Receiving Information: Effective Listening, Interviewing & Analyzing.

* Personal Effectiveness: Negotiation, Conflict Resolution, Influence and Motivation, Judgment, Facilitation.

* Professional Education & Training: Identification of Training Needs & Behavior Change Techniques.

* Leadership: Meeting Chairing, Facilitation, Team Building & Process Definition.

* Recognition, Networking & Code of Ethics.

Building the Test Environment:
* Test Standards: External Standard & Internal Standards.

* Test Environment Components: Test Process Engineering, Tool Development and Acquisition, Acquisition or Development of a Test Bed / Test Lab / Test Environment.

* Test Tools: Tool Competency, Tool Selection (from acquired tools).
* Quality Assurance / Quality Control: Quality Assurance versus Quality Control, Process Analysis and Understanding.

* Building of Test Environment Work Processes: Concepts of work processes, Building a Test Work Process, Test Quality Control, Analysis of the Test Process & Continuous Improvement.

* Adapting the Test Environment to Different Technologies

Risk Analysis:
* Risk Identification: Software Risks, Testing Risks, Premature Release Risk, Business Risks & Risk Methods.

* Managing Risks: Risk Magnitude, Risk Reduction Methods & Contingency Planning.

Test Planning Process:
* Pre-Planning Activities: Success Criteria / Acceptance Criteria, Test Objectives, Assumptions & Entrance Criteria / Exit Criteria.

* Test Planning: Test Plan, Requirements / Traceability, Estimating, Scheduling, Staffing, Approach & Test Check Procedures (i.e., test quality control).

* Post-Planning Activities: Change Management, Versioning (change control / change management / configuration management).

Test Design:
* Design Preparation: Test Bed / Test Lab & Test Coverage.

* Design Execution: Specifications, Cases, Scripts & Data.

Performing Tests:
* Execute Tests

* Compare Actual versus Expected Results

* Test Log

* Record Discrepancies

Defect Tracking and Correction:
* Defect Tracking: Defect Recording, Defect Reporting & Defect Tracking.

* Testing Defect Correction: Validation, Regression Testing & Verification.

Acceptance Testing:
* Concepts of Acceptance Testing

* Roles and Responsibilities

* Acceptance Test Process

Status of Testing:
* Test Completion Criteria: Code Coverage, Requirement Coverage.

* Test Metrics: Metrics Unique to Test, Complexity Measurements, Size Measurements, Defect Measurements & Product Measures.

* Management by Fact

Test Reporting:
* Reporting Tools

* Test Report Standards

* Statistical Analysis
--------------------------------------------------------------------------

The Introduction of this preparation guide explained a process for you to follow to prepare for the examination. It emphasized familiarizing yourself with a Common Body of Knowledge (CBOK), the vocabulary of software quality, the activities performed by testing professionals, and reviewing several other different references that are included on the software certifications Web site. Other references you might look at include articles in professional IT publications.

If you feel you are ready to take the examination, you need to schedule the examination. Be sure to visit www.softwarecertifications.org for up-to-date CSTE examination dates and places. Once scheduled, the remaining event is to take the examination.


CSTE Examination Overview
The four and a half hour examination consists of four written parts, including multiple-choice and essay questions. A typical CSTE examination is comprised of two parts for Software Testing Theory and two parts for Software Testing Practice:

Software Testing Theory
Part 1 (Approximately 50) multiple-choice questions (Complete within 45 minutes)
Part 2 (Approximately 10) essay questions (Complete within 1 hour, 15 minutes)
Software testing theory evaluates your understanding of testing principles, practices, vocabulary and concepts. In other words, do you have a solid foundation in testing basics? For example, can you differentiate between verification and validation?


Part 3 (Approximately 50) multiple-choice questions (Complete within 45 minutes)
Part 4 (Approximately 10) essay questions (Complete within 1 hour, 15 minutes)

Software testing practice evaluates whether you can apply testing basics to real-world situations.

For example, a question may be: “What methods of quality control would you use to reduce defects for a software system under development? During which phase of development would you use those methods?”
You cannot bring any study or supporting materials to the examination site other than a pencil.

Each individual will have an assigned seat. You may take a 15-minute break between each examination part, but not during the examination.

Proctors for the examination are not required to be certified. If not certified, they are ineligible to take the examination for at least two years after proctoring. Proctors follow specific instructions to conduct the examination. Software Certifications’ policies and procedures enforce confidentiality and security of the examination instrument, prior to and after the examination.

SPONSORED LINKS

Comments :

1

Very Informative.. thanx so much!! I am looking at giving CSTE sometime in feb '09.
I had a concern though.... most of the Q papers I see online are a little old, like '05 & '06. Are those Q papers still relevant? Do the Qs repeat? Do you, by any chance, have access to any '08 Q papers?? Thanx a tonne in advance!!!

Ramya's Mane Adige said...
on 

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Impact Analysis Checklist for Req. Changes
___    Implications of the Proposed Change* Identify any existing requirements in the baseline that

The Process of Test Process Improvement

Software testing is still a pain-in-the-neck for many organizations. Because it is only marginally addressed in software process improvement models like CMMi

 

Software Defect-bug Management Philosphy

Imperfect processes cause most of the software defects. Thus to prevent defects, the development process needs to be overhauled.

 

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Blog Archive