Quality assurance

The QA process in our company usually consists of 3 phases.

The startup phase is targeted mostly to documentation artifacts of the project. During this phase QA experts together with development experts analyze the requirements and specification documents in order to eliminate any inconsistencies. Also some new functionality may be offered to extend the required features in order to improve the entire application. QA engineers also analyze different testing approaches and techniques, estimate the resources for them, approve the format of all QA related documents and create first versions of test plans. During the main phase of QA process testing itself takes place, QA artifacts are being created, testing repositories are created, automated tests are developed and executed, found defects are detected and reported, fixes verified, QA documents are completed and maintained. Release phase represents QA activities when software product is about to be deployed to production environment or a new version of software is about to be delivered to customers or end users. It includes assessment of testing coverage, acceptance testing, goal meeting validation, review and approval of release notes and transition of QA artifacts.

QA process with lack of documentation.

The normal QA process assumes that development of the entire project is made with all necessary documents such as vision documents, requirements, specifications at different levels. However not all software products are developed using these practices. Often rather small projects are developed without the initial documentation and project features are discussed by development teams on meetings in order to save time required for documents creation.

Smartech QA team has experience in handling such projects and has modified QA process for software products that are not “traditional” black-box ones. According to these specific conditions some major QA activities are moved from certain phases to different ones, and the complete set of activities is slightly different.

During the startup phase QA effort are targeted mostly to investigation of the software product, because the only source of information is application itself. The following efforts take place during the phase: acquaintance with product, investigation of product modules, research of 3-rd party components, initial product testing, definition of testing approaches and rough resource estimation. Often products are reverse-documented during this phase. The main and release phase of QA process with lack of documentation does not differ much from usual QA process and includes the same steps described above.