Quality Assurance

Quality Assurance (QA) at Gloonark Technologies is more than just a process or a position - it is a practice. Of course our practice includes testing; however, it also includes much more. It includes developing techniques and using tools to ensure quality in the development process, not just testing after the fact. At Gloonark Technologies QA is a mind-set that quality and testing are not someone else's job but all of our jobs.

Given the importance of testing as part of quality we want to share some aspects of our approach. One important way we ensure quality is by using the Gloonark Platform the testing requirements of many aspects of the architecture are greatly reduced. The Gloonark Platform has already been through rigorous testing in many different applications. Another aspect of our approach is that testing is not only completed by the developer who wrote the code, but by the entire project team. Our development methodology lends itself more easily to integration testing and testing the communication between developers' work. Our development practices include things like building test harnesses and writing test scenarios and test scripts which also improve the quality of the work along the way. Throughout the project and again as a final check after testing is completed, the team leader and/or director will walk through the requirements documentation to ensure that functionality was not missed or misinterpreted.

These are only some of the aspects of Quality Assurance at Gloonark Technologies. There are many more including continuous integration, iterative testing, cross Web browser testing, setting up test environments and version control, code reviews, performance testing, deployment scripts and others.
In summary, we value quality assurance and appreciate and understand creating the right balance of testing in the scope of the project budget.