MetaBoss
User Guides
Synopsis
Beginner's Guide
Configuration Guide
Design Studio Guide
Programming Model Guide
Testing Framework Guide
'How To ...' Guides
References
Synopsis
Design Model Reference
Design Model UML Profile
Test Schema Reference
MetaBoss design library
Run-time libraries API
Dev-time libraries API
HatMaker Example
Synopsis
Enterprise Model Description
Enterprise Model Reference
SystemTest Example
WebServices Example
Miscellaneous
About MetaBoss
Quality Assurance
Compatibility Notes
Acknowledgments
Glossary
Change Log
Version 1.4.0001
Built on 15 Dec 2005 22:31:47

Quality Assurance

At MetaBoss we approach software manufacturing very seriously and do everything possible to ensure that MetaBoss releases are always of high quality and that each and every new release has not degraded any of the existing features of the product.

Centrepiece of our quality assurance policy is the automatic regression testing which occurs at the end of every product build. If the build,test,release process fails at any step - release is aborted, problem is rectified and whole build process is repeated from the beginning. In other words we automatically test lots of features prior to the release and never knowingly make faulty releases.

How do we test and what do we test? Interestingly enough we actually use MetaBoss to test MetaBoss. This process works as follows:

  1. Core MetaBoss product is built from source and deployed to our automatic test environment. This build is a full clean build from scratch.
  2. Sample applcation is fully generated from the model, built and deployed to our automatic test environment. This step tests model repository, code generation and quality of our sample deployment scripts.
  3. Large number of Test Cases with known results are executed against each and every type of database MetaBoss supports. This step tests the System Testing Framework itself as well as useability and quality of the generated code.
  4. The results of these Test Cases are fully checked against previosly saved specimen results. This step tests the Regression Testing Framework itself as well as useability and quality of the generated code.

Our goal is to grow the number and range of Test Scenarios and to keep them relevant. In order to achieve that our policy is to reproduce any reported bug in the TestCase before fixing it and insert the newly created TestCase in the regression test TestScenario. In addition, we are open to suggestions or requests from our users to include certain Test Cases in our regression test.

To make our Quality Assurance process transparent and verifiable by our users, we are automatically copying the test logs into the documentation and have introduced this page where anyone can always verify the results of the tests conducted automatically during the MetaBoss build.

This link will take you to the folder where Test Logs of all tests which were automatically executed during this release are stored.