PeopleCert Certified Software Tester (CSTE) Exam Questions

PeopleCert Certified Software Tester Exam Exam Objectives

1. 1

   1.0 Software Testing Principles and Concepts

   • Skill 1.1.1: category focuses on the ‘basics’ of software testing as represented by the vocabulary of testing, testing approaches, methods and techniques as well as the materials used by testers in performing their test activities.
2. 2

   2.0 Building the Software Testing Ecosystem

   • 2.1The test ecosystem is comprised of all the conditions, circumstances, and influences surrounding and affecting the testing of software.
3. 3

   3.0 Managing the Test Project

   • 3.1Software testing is a project with almost all the same attributes as a software development project. This category discusses project planning, project staffing, scheduling and budgeting, communicating, assigning and monitoring work and ensuring that changes to the project plan are incorporated into the test plan.
4. 4

   4.0 Risk in the Software Development Life Cycle

   • Skill 4.1.1: category explains the concept of risk which includes project, process, and product risk. Understanding risk is required in order to evaluate whether the controls are in place and working in the development processes and within the application under test.
5. 5

   5.0 Executing the Test Plan

   • Skill 5.1.1: category explores the skills testers need to plan tests, including the selection of techniques and methods to be used to validate the product against its approved requirements and design. Testers must understand the development methods and environment to effectively plan for testing.
6. 6

   6.0 Walkthroughs, Checkpoint Reviews and Inspections

   • 6.1The importance of integrated quality control throughout the development life cycle cannot be understated. Often testing is only described in terms of dynamic test case execution. In this section of the STBOK, an in-depth discussion about the static testing techniques of walkthroughs, checkpoint reviews and inspections is given.
7. 7

   7.0 Designing Test Cases

   • Skill 7.1.1: category covers identifying test conditions from specifications documents, test transaction types, Use Cases, and Agile User Stories. Further detailed are the techniques to develop test cases from the test conditions using such white box techniques as branch condition and data flow. Black box test cases designed based on techniques such as equivalence partitioning and all-pairs testing are explained in detail.
8. 8

   8.0 Executing the Tests

   • 8.1Testing should commence when the project commences and conclude when the software is no longer in operation. This category focuses on the many skills needed to execute the tests from Acceptance Testing across the SDLC, Unit, Integration and System testing as well as User Acceptance Testing (UAT) and testing Commercial Off-The-Shelf (COTS) software.
9. 9

   9.0 Measurement Test Status, Analysis and Reporting

   • 9.1In this category the tester’s ability to develop testing status reports is discussed. These reports should show the status of the testing based on the test plan. Reporting should document what tests have been performed and the status of those tests. The test reporting process is a process to collect data, analyze the data, supplement the data with metrics, graphs and charts and other pictorial representations which help the developers and users interpret that data. The lessons learned from the test effort should be used to improve the next iteration of the test process.
10. 10

    10 Testing Specialized Technologies

    • Skill 10.1.1: category addresses specilized technologies of web application testing, mobile application testing, Cloud base applications, testing within an Agile framework, DevOps application testing, and the Internet of Things.