Duration
3 days
TARGET AUDIENCE
The target audience for the program are the ones who are involved with any / all / either of the functions given below:
- Test Engineering;
- Test Manager
- Requirements Analysts
- Software Developers
- Project Manager
OBJECTIVES
The CSTE program establishes the standards for initial qualification and continuing improvement of professional competence. After the completion of the course, the participants would be able to:
- Define the tasks (skill categories) associated with software quality assurance duties in order to evaluate skill mastery.
- Demonstrate an individual’s willingness to improve professionally.
- Acknowledge attainment of an acceptable standard of professional competency.
- Aid organizations in selecting and promoting qualified individuals.
- Motivate personnel having software quality assurance responsibilities to maintain their professional competency.
- Assist individuals in improving and enhancing their organization’s software quality programs (i.e., provide a mechanism to lead a professional).
COURSE OUTLINE
INTRODUCTION TO CLASS
- Familiarization with course material
- Familiarization with the protocols and timings
- Expectation setting and clarifications
KNOWLEDGE CATEGORY 1 ~ SOFTWARE TESTING PRINCIPLES AND CONCEPTS
This skill 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.
KNOWLEDGE CATEGORY 2 ~ BUILDING THE SOFTWARE TESTING ECOSYSTEM
The test ecosystem is comprised of all the conditions, circumstances, and influences surrounding and affecting the testing of software.
KNOWLEDGE CATEGORY 3 ~ MANAGING THE TEST PROJECT
Software 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.
KNOWLEDGE CATEGORY 4 ~ RISK IN THE SOFTWARE DEVELOPMENT LIFE CYCLE
It is often stated that a primary goal of a software tester is to reduce the risk associated with the deployment of a software application system. The very process of test planning is based on an understanding of the types and magnitudes of risk throughout the software application lifecycle. This skill 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.
KNOWLEDGE CATEGORY 5 ~ EXECUTING THE TEST PLAN
This skill 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.
KNOWLEDGE CATEGORY 6 ~ WALKTHROUGHS, CHECKPOINT REVIEWS AND INSPECTIONS
The 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.
KNOWLEDGE CATEGORY 7 ~ DESIGNING TEST CASES
This section of the STBOK defines the procedures to identify individual test conditions, decompose the test conditions into individual test cases and create test scripts. The skill 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.
KNOWLEDGE CATEGORY 8 ~ EXECUTING THE TESTS
Testing 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.
KNOWLEDGE CATEGORY 9 ~ MEASUREMENT TEST STATUS, ANALYSIS AND REPORTING
In 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.
KNOWLEDGE CATEGORY 10 ~ TESTING SPECIALIZED TECHNOLOGIES
Testers require skills in their organization’s current technology, as well as a general understanding of the new information technology that might be acquired by their organization. Testing new technology creates some unique challenges which would not be an issue once the new technology is fully assimilated. There are many specialized technologies, new or otherwise, which require specific skills to test. This skill category addresses specialized technologies of web application testing, mobile application testing, Cloud base applications, testing within an Agile framework, DevOps application testing, and the Internet of Thing.
CASE STUDY, EXERCISES & QUIZZES
Programme scope, delivery arrangements and suitability are confirmed during enquiry.