Document Study : All the documentation for the understanding the application like SRS, Design Document, User manuals.
Test Planning : Kiwi QA Engineer plan for test which include defining test Strategy,identification of component what is to be tested or what not to be tested,identification of testdata and test process. Also it include identification of open source defect tracking tool, estimation for testing and preparing schedule for testing.
Prepare TestCases : Based on the understanding of the application from the study of documents, test cases would be written. These testcases would then be reviewed for accuracy and coverage.
TestData Creation: This is probably the most important part of testing. We study the system from the endusers point-of-view, and derive the test data based on this understanding. We try to rope in or create as much real data as possible for testing.
Test Environment: For setting up the test environment, Kiwi QA lead select most appropriate resources are selected and configured as per the need of the test case.
Test Execution : When we receive a build for Testing, we would first run the Sanity Tests to check whether the build is testable or not. If the software fails the Sanity Tests, we would report the corresponding issues/defects. Only after the build passed the Sanity Tests, we would proceed for executing comprehensive Test cases.
Results Analysis : At KiwiQA, the testers would strive to isolate the problem as much as possible and prepare a comprehensive defect report.
