We should come to terms with the fact that software is everywhere. From vehicles to consumer household products. From manufacturing lines to information technology systems. These software products will require testing. We see the consequences of poor software testing in newspapers and magazine articles. We end up with costly product rework or recalls. We lose customers our reputation is tarnished. Many things impact the quality of the product. Ideally, testing provides feedback on the software throughout development uncovering defects and other mal performance issues allowing the developers to make the requisite changes. Software testing is fundamental to assuring a quality product. The quality of that testing is based upon the engagement and competence of those testing the software.
What do you think test cases are? What are the steps necessary for testing the product? As a manager of a burgeoning testing department at a large company, my team was 15 people strong. I recognized that developing a common understanding of software testing and a depending consequence of general product testing. This common mental model and lexicon would provide a base upon which we could build. Developing a common understanding has many advantages, not the least of which is having some degree of confidence in our communication. That is, we know what the other team member is saying. The certification was not so important to me as a manager. I thought it important for the team members, to provide a second objective assertion of the team members’ accomplishment and competency. We all went to a software testing certification class. I did not require nor push the team members to sit for the exam. Most of the team acquired the certification.
This class will provide those attending with additional tools to put into their repertoire, or as we like to call it, your backpack. From experience, product testing is often compressed (and sometimes compromised) by time to market pressures. Knowing more shortens the time for testing. This happens by making better use of the time before the software is available for testing. The techniques demonstrated also reduce time by starting quality assurance activities in which the test personnel should be included. All of this will provide a basis for continuous learning over your testing career.
The benefits to the organization:
- Better quality products through a comprehensive approach to software testing (static techniques) = reduced defects in the field.
- A variety of software testing approaches find a variety of defects
- Learn methods to optimize testing to ensure test coverage even when time for testing is compressed
- Fewer defects
The benefits to the student
- Higher earning capacity (some estimates 20%)
- Differentiation of your level of proficiency
- Additional tools help reduced stress during trials of testing
Value Transformation has decades of software testing experience, including preparation for CTFL. Software testing is core to product development and done ineffectively, will cost the customer and company dearly. The world is full of examples where testing is done poorly and has consequences on the organization and customers. Delivering a poor-quality product to the customer is not in anybody’s interest. Effective testing, especially of software products, can be complex and is not the sort of thing that happens at the end of product development.
The training will be a combination of virtual classrooms and self-study. The class will consist of 4 hours of instructor classroom engagement per day. The expectation upon the student is to put in an additional 2-4 hours per day with presentation material, quizzes, and games, before the classes with the team.
The instructor will present in a virtual classroom at the Value Transformation training portion of the website, using the Big Blue Button or another virtual classroom tool. Questions, quizzes, and discussion boards will be accessible from this location. Each student will receive specific login credentials, along with grades for the quizzes and puzzles. The students will have access to the material for 60 days to allow the student to continue to prepare for their respective certification exams.
2022 Course Dates
- Course 1 Oct 3-6, 2022 – 1pm – 5pm Eastern US
- Module 1 – Fundamentals of SW testing
- Module 2 – Testing throughout the SW cycle
- Oct 4
- Module 3 – Static Techniques
- Oct 5
- Module 4 – Test Design Techniques
- Oct 6
- Module 5 – Test Management
- Module 6 -Tools Support for Testing