Skip to main content

Conformance Testing

Conformance Testing verified that the application perform according to the specified standards. Conformance Testing is a method to specify that the product, system meets the specified standards. Conformance Testing is also know as Compliance Testing.

Conformance Testing is the Non Functional Testing. In some companies there are some standards for the organization so when the product is developed those people will check that the product meeting the standards of the organization. They put the check over product to verify the standard of the product.

For Conformance Testing, a set of procedure will specified for each phase of software development life cycle. so when any phase completed then people will check that whether that completed phase meets the standards and put the gaps if they found any. People apply those standards for every phase of software development life cycle and note if find out any gap.

In an organization there are many Compliance like Performance, Robustness, Behavior, Documentation, Operations and Interoperability but the difference between these and Compliance Testing that it checks that implementation should meet the requirement of a standard and specification.  

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.