Dev/QA/Testing Procedures

Terra Dotta employs a team of dedicated QA specialists for regular and ongoing testing of our applications, targeting stability, security, usability, performance and data integrity. The team analyzes new and modified functionality to create and maintain test plans for every major and minor release as well as for patches. Testing is performed manually and with automated tools. Manual test cases are executed according to standard, regular routines, as well as ad hoc tests. The Terra Dotta annual major-release cycle entails the following processes:

  • Analysis: Requirements are written into functional specifications.
  • Architecture: Technical specifications (design and data modeling) with team review.
  • Implementation: Code development.
  • Preliminary functional testing: Initial development is checked against specs for accuracy.
  • Alpha testing: Code is tested to identify major flaws and returned for corrections.
  • Beta testing: New build with alpha corrections is retested (full regression). Testing sites are opened to the user community for review and feedback.
  • Release-candidate testing: New build with Beta corrections undergoes additional regression testing. Code is certified for release.

Each of the test phases may entail additional regression as needed. Example: It is common for a "Beta 2" phase to be performed if significant or numerous issues are found in the Beta phase.

With any release, there is the possibility of issues discovered in production. Terra Dotta analyzes the impact of any reported issues and determines whether the need exists for a maintenance patch. Patches are subject to unit and integration testing before their release. Periodically, Terra Dotta may elect to issue a maintenance/minor release between major releases, encompassing all prior and current patches. Such releases undergo the same suite of testing as our major releases.