Syllabus for Certified Software Tester

8) Syllabus for Certified Software Tester
The Certified Software Test Exam concentrates more on the following areas:
• Knowledge on the Test Environment.
• Ability to plan tests.
• Ability to execute tests, design test cases, use test tools, etc.
• Ability to develop testing status reports.
Skill Categories: The basic categories to be concentrated while preparing for CST exam are summarized as follows:
Test Principles and Concepts: Definition of Test Specifications, Testing Techniques, Testing Methods, Independent Testing, and Commercial off the Shelf (COTS) Software, Testing Code Developed under outside Contract, Test Quality, Testing Life Cycle, and Technical terms of testing.
Tester’s Role in Software Development and Acquisition:
1. The Development and Acquisition Process: Process Knowledge – Knowledge on Software Development, Operation, and Maintenance Process, Tools, Project Management, Test Documentation and Roles/Responsibilities.
2. Test Approaches: Structural Test Approaches, Functional Test Approaches.
3. "V" Testing Concept
4. Quality Attributes.
Test Management:
1. Test Management: Test Objectives, Test Competency, Test Performance, Test Technology, Staffing, Management of Staff.
2. Giving Information: Audience Evaluation, Effective Presentation, Written Correspondence, and Oral Delivery.
3. Receiving Information: Effective Listening, Interviewing, Analyzing.
4. Personal Effectiveness: Negotiation, Conflict Resolution, Influence and Motivation, Judgment, Facilitation.
5. Continuing Professional Education: Identification of Training Needs, Behavior Change Techniques.
6. Leadership: Meeting Chairing, Facilitation, Team Building, Process Definition.
7. Recognition, Networking, Code of Ethics.
Build the Test Environment:
1. Test Standards: External Standard, Internal Standards.
2. Test Environment Components: Test Process Engineering, Tool Development and/or Acquisition, Acquisition or Development of a Test Bed/Test Lab/Test Environment.
3. Test Tools: Tool Competency, Tool Selection (from acquired tools).
4. Quality Assurance / Quality Control: Quality Assurance versus Quality Control, Process Analysis and Understanding.
5. Building the Test Environment Work Processes: Concepts of work processes, Building a Test Work Process, Test Quality Control, Analysis of the Test Process, Continuous Improvement.
6. Adapting the Test Environment to Different Technologies
Risk Analysis:
1. Risk Identification: Software Risks, Testing Risks, Premature Release Risk, Business Risks, Risk Methods.
2. Managing Risks: Risk Magnitude, Risk Reduction Methods, Contingency Planning.
Test Planning Process:
1. Pre-Planning Activities: Success Criteria/Acceptance Criteria, Test Objectives, Assumptions, Entrance Criteria/Exit Criteria.
2. Test Planning: Test Plan, Requirements/Traceability, Estimating, Scheduling, Staffing, Approach, Test Check Procedures (i.e., test quality control).
3. 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:
1. Execute Tests
2. Compare Actual versus Expected Results
3. Test Log
4. 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



8 April 2009 at 23:42

Your Blog is very very informative..
Keep Going..

Post a Comment

Who ever writes Inappropriate/Vulgar comments to context, generally want to be anonymous …So I hope U r not the one like that?
For lazy logs u can at least use Name/URL option which don’t even require any sign-in, good thing is that it can accept your lovely nick name also and URL is not mandatory too.
Thanks for your patience
~Best job portal admin(I love "Transparency")