Home » Testing
CMST



The Certified Manager of Software Testing (CMST) certification establishes a worldwide standard for the assessment of the capabilities and competencies of software testing professionals that are working at, or soon will work at, the software testing management level.

Acquiring the designation of CMST indicates a level of professional competence in both the principles and practices of software testing, demonstrating the skills and capabilities necessary to manage the software test function. The CMST certification provides IT upper management a necessary tool to predict the likelihood of success of individuals applying for management level positions. The CMST certification also provides the IT professional with an objective assessment of their management skills.

Examination Availability: (CMST)
The CMST certification exam is currently ONLY available in the following areas

Belarus, India, and Sri Lanka.

To qualify for candidacy, each applicant must:
•    Currently hold an activeCSTE Certification (recommended, not required).
•    Be working in the field covered by the certification designation.
•    Have the experience to demonstrate mastery of the skills identified in the current Software Testing Common Body of Knowledge(CBOK) and be prepared to submit Real-World Experience documentation that supports your experience in the software testing field.
•    Be prepared to take the required manager’s level examination.

AND meet one of the following three prerequisites:
1.    A bachelor’s degree from accredited college-level institution & 4 years of experience in the software testing field
2.    An associate degree & 6 years of experience in the software testing field
3.    Eight years of experience in the software testing field.
An applicant for certification must adhere to the Code of Ethics that outlines the ethical behaviors expected of all certified professionals by the ISCB.

The CMST application fee is:
•    $450.00

The application fee includes the following:
•    Instant access to a PDF file of the CMSTCBOK (561 pages) which is a useful tool to help prepare for the exam. After payment go to the CBOK Manuals page of Customer Portal for access.
•    The candidateInitial Exam which must be taken within one year from the date payment was processed or the application will expire

Examination Details: (CMST)
The exam itself is paper-based consisting of four parts - constructed response (essay) questions. The examination tests the candidate’s “practical” knowledge in the following four areas:
1.    Test Management
2.    Test Analysis
3.    Test Planning and Execution
4.    Communications and Relationships
The exam will take over 4 hours to complete which includes a 10 minute break after the first three parts. The passing mark is 75% which is the average score of both parts.

If you had an activeCSTE certification at the time of applying for the CMST, once you become a CMSTcertificant then your CSTE will remain active and mirror the CMST as long it remains active. CSTE certifications are not subject to reactivation if expired prior to applying for the CMST certification.

IMPORTANT:
Until the Real World Experience documentation has been submitted and approved by the ISCB the candidate will NOT be able to schedule their CMST exam.

Recertification
To maintain the CMST certification, it is a requirement that the certified manager continue to mature their technical and managerial competencies. Certified managers must earn 30 CPE (continuing professional education) points in each of the following four categories every three years (120 CPE total in three years):
•    Management Skills (30 CPE / 3 years)
•    Technical Skills (30 CPE / 3 years)
•    Professional Development Activities in the Industry (30 CPE / 3 years)
•    Additional activities in selected categories (30 CPE / 3 years)

Test Case !!!

A test case specifies the pretest state of the IUT (Integration Unit Testing) and its environment, the test inputs or conditions, and the expected result. The expected result specifies what the IUT should produce from the test inputs. This specification includes messages generated by the IUT, exceptions, returned values, and resultant state of the IUT and its environment. Test cases may also specify initial and resulting conditions for other objects that constitute the IUT and its environment.”

In software engineering, the most common definition of a test case is a set of conditions or variables under which a tester will determine if a requirement or use case upon an application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied. In order to fully test that all the requirements of an application are met, there must be at least one test case for each requirement unless a requirement has sub requirements.

* Test cases help us discover information. Different types of tests are more effective for different classes of information.
* Test cases can be “good” in a variety of ways. No test case will be good in all of them.
* People tend to create test cases according to certain testing styles, such as domain testing or risk-based testing. Good domain tests are different from good risk-based tests.

Basics of Software Testing !!!

CHAPTER 1

Basics of Software Testing
****************************

THE DEFINITION OF TESTINGTesting is a process designed to
• Prove that the program is error free
• Establish that the software performs its functions correctly
• Establish with confidence that the software does its job fully

Concepts - Testing is the task of locating errors.

GOALS OF TESTING1. Find cases where the program does not do what it is supposed to do.
2. Find cases where the program does things it is not supposed to do.
The first goal refers to specifications which were not satisfied by the program while the second goal refers to unwanted side-effects.
Defects:
  • Not satisfying the Customer’s requirements.
  • Variance from the desired product.
  • Expected result is not equal to actual result.
It is defined as the lack of something necessary or desirable for completion or perfection. In other words, An imperfection that causes inadequacy or failure,

Defect Status
New Defect - Defect detected recently.
Open - Defect open for rectification.
Fixed - Open for rectification but not yet rectified.
Reopen - Again open for rectification.
Closed - Defect is rectified.
Rejected - Defect cannot be rectified.

Defects severity
Critical - we cant proceed with the application.
Major - we can proceed with the application.
Minor - Defects are negligible.

Defects priority
High - If it is critical
Medium - If it is major
Low - If it is Minor
Software Testing:
* Process of evaluating defects in a software application.
* Software testing is a process of analyzing or operating software for the purpose of finding bugs.
* According to the definition, testing can involve either "analyzing" or "operating" software.
* Test activities that are associated with analyzing the products of software development are called static testing. Static testing includes code inspections, walkthroughs, and desk checks.
* In contrast, test activities that involve operating the software are called dynamic testing.
* It’s a process of evaluating the system by manual or automation means and verifies that it satisfies specified requests and identifies the difference between expected and actual results.
Why Software Testing?
  • Software Testing is important as it may cause mission failure, impact on operational performance and reliability if not done properly.
  • Effective Software Testing delivers quality products satisfying user’s requirements, needs and expectations.
  • To unearth and correct defects.
  • To detect defects early and to reduce cost of defect fixing.
  • To ensure that product works as user expected it to.
  • To avoid user detecting problems.
Participants of Software Testing:
  • Software Customer.
  • Software User.
  • Software Developer.
  • Software Tester.
  • Information service management. (Group of people who gathers information from customers)
  • Senior Organization management. (Team leader and project leaders)
Basic Testing Types:

Static - review of documents.

Dynamic
Types
Functionality : Testing Functionality of application
Performance : Testing performance of the application