 |
|||||||||||
|
 |
|
|
For over 20 years Software Quality Methods, LLC. has prepared and presented public and private courses on software testing, test automation, quality assurance, engineering management, and information technology. Public courses are available periodically through AST, ASQ, and UCSC-Extension. Private corporate classes can be customized to fit organizational standards, environments, and content requirements.
Brief Course DescriptionsBlack Box Software Testing (Classroom)This classroom course presents a pragmatic approach to black box testing, using examples derived from experience with a broad spectrum of applications on a number of different operating systems. It covers basic and advanced issues ranging from an overview of software development and testing to a management-level analysis of the risks and trade-offs associated with starting a GUI-level test automation project. Students completing this course will have been given a brief tour of the basic information needed to design, plan, and conduct black box testing. The class consists of eight half-day or four full day sessions. (Detailed outline) Required Text: Testing Computer Software, Cem Kaner, Hung Nguyen, and Jack Falk (TCS on Amazon) Return to Top Black Box Software Testing - Foundations (Online)This online course presents a context-driven approach to black box testing. The course is designed to teach about testing using recorded lectures, quizzes, discussions, and assignments. With instructor guidance, students discuss and critique some of the most important questions and issues in software testing. It covers basic and advanced issues and considers:
The class consists of eight half-week asynchronous sessions. Each student chooses when they do their work but assignments are interdependent with hard due dates. A minimum of ten students are required in a class since they review and discuss work submitted by one anther. (Detailed outline) Bug Reporting and Bug Management (Online)This on-line course presents an experiential approach to reporting bugs and influencing getting them fixed. The course is designed to teach about testing using recorded lectures, quizzes, discussions, and assignments. With instructor guidance, students analyze and create bug reports as class exercises. Key aspects of this course include:
The class consists of eight half-week asynchronous sessions. Each student chooses when they do their work but assignments are interdependent with hard due dates. A minimum of ten students are required in a class since they review and discuss work submitted by one anther. (Detailed outline) Test Oracles (Classroom)One of the most difficult things about software testing is determining whether or not software behavior is correct. The mechanism used to make that determination is called a test oracle. This course shows the kinds of oracles available and methods to use them. Student completing this course will understand the role of oracles in software testing and the practical application of that knowledge. (Detailed outline) Automated Exploratory Testing (Classroom)This course describes how to design powerful automated tests that can discover bugs that manual testing cannot. The approach looks at test mechanisms that explore program characteristics using automation. Exploration occurs because the tests use techniques to go well beyond automating manual regression tests. When used effectively, these automated tests can detect difficult, elusive bugs and find more than automated regression tests. Student completing this course will come away with an approach to design of automated tests based on available oracles. (Detailed outline) Test Automation Architectures (Classroom)This class provides an overview of how to design a test automation framework. Although automated software testing has been done for decades, software test automation efforts still frequently fail for numerous reasons (see Cem Kaner's paper from the Los Altos Workshop on Software Testing). Often, organizations only realize in hindsight that they would have done more and better manual testing if the effort invested in test automation had instead been used to design and run tests. Even more frequently, automated tests require fixing or complete replacement as soon as the release is complete. The key to good return on automation investments is through understanding the things test automation can and can't do, planning for test automation, and engineering the automated tests. Many failed test automation initiatives we have seen would not have been begun if the long term return on investment had been considered. (Detailed outline) Recommended Text: Lessons Learned in Software Testing, Cem Kaner, James Bach, and Brett Pettichord (Lessons Learned on Amazon) CSQE Examination Preparation (Classroom)This class provides an overview of materials in the ASQ’s Certified Software Quality Engineer (CSQE) 2008 body of knowledge (BOK) and teaches how to convert an understanding of the vocabulary and subjects into the ability to answer typical exam questions for the ASQ CSQE examination. The class consists of eight half-day or four full day sessions. Although students will review all areas of the BOK, coverage in depth of any particular area is not possible due to time constraints. (Detailed outline) Required Text: CSQE Primer, Barbara Frank, Phil Marriott and Chett Warzusen (Quality Council of Indiana)
Updated July 1, 2011 Copyright © 1995-2011 Software Quality Methods, LLC. All Rights Reserved. |
| [Home] [About Us] [Services] [Managerial] [Training] [Technical] [FAQ] [Papers] [What people say...] [Associates and Links] |