PragmaTest Process

Organizations today face a time crunch. There is less time and more work always. Losing quality is losing customers. Planning for quality and automation don’t solve all the problems. Traditional quality assurance methods help but are they most efficient? Do they take care of all aspects of quality?

More often than not, a simple answer to these questions is “No”?

What is PragmaTest?

PragmaTest is a simple and realistic approach to testing. It is not possible for any organization to cover all the aspects of quality in every build using traditional models. PragmTest combines the best practices of testing intelligently and efficiently to give maximum test coverage in minimum time.

How does it work?

PragmaTest divides quality assurance in to 3 parts

  • PragmaPrep
  • PragmaTest
  • PragmaRelease

PragmaPrep :

PragmaPrep is where we do a validation and preparation before we begin our testing process. PragmaPrep ensures basic quality checks are done before a build goes to PragmaTest. PragmePrep starts with a developer checking-in the code

  • Monitor check-in using check-in policies to ensure that there is no poor quality code is checked in.
  • Integrate build with a code quality analysis process to ensure high levels of code quality.
  • Automate smoke tests verify basic tests that have to be passed before a build goes to a test engineer for testing.
  • Execute unit tests with every build and monitor code breaks.

PragmaTest

PragmaTest starts with successful builds thus saving time, effort and cost by testing only builds that have successfully passed Pre-QA analysis.

  • Execute tests of successful builds in key environments.
  • Execute internationalization and localization tests.
  • Automate regression tests to reduce the effort of repeated testing.
  • Intelligent Regression. Regress test only code that has changed and parts of application affected by the change using our special regression tools.

PragmaTest Benefits
1.Continuous automation to drive down effort.
2.Identify risks early in the lifecycle.
3.Intelligent regression that drives down the regression effort.

PragmaRelease

PragmaRelease starts the completion of PragmaTest cycles with the software reaching a feature complete

1.Execute performance, reliability and scalability tests.
2.Execute data migration tests.
3.Execute certification tests if applicable.
4.Execute live tests with key customers to validate in live environment.

PragmaRelease Benefits
1.Continuous automation to drive down effort.
2.Identify risks early in the lifecycle.
3.Intelligent regression that.

What is the big deal?

Everything above sounds just simple. What is the big deal about it? Nothing! Nothing at all! There are no revolutionary ideas in the list above. There is no promise of bringing moon to the earth. That is exactly why it is pragmatic. But, the key question is, have you been able to set this up? While the whole process sounds simple, it needs specialists with the right skills to set it up. Setting up build automation and integrating code quality analysis, test automation, certifications testing etc. require the right skills to set up and run.
It is important also to be able to collect and build intelligence from metrics. Collecting metrics is only a part of the job but to implement best practices based on the metrics is what makes the process is complete and useful.

Conclusion

Combine the PragmaTest with our Testing as a Service model; you have a winning combination at hand. The results are:

  • Low cost
  • Low maintenance
  • Low risk
  • High efficiency