As a test engineer, almost every time a question should be asked of the interview is to talk about your company's project - testing process. Do not silly to say nothing of our company processes, or, agile development, the process is very simple, so basically you pass out. But it is still a basic framework for the process of it, in the following order:
Project -> write requirements -> Requirements Review -> identify needs -> Test Plan -> test case writing (R & D R & D write a) -> Use Cases Review -> integration testing -> first round function testing -> a second round of functional tests (which may include performance, security, regression testing) -> third round function tests (which may include performance, security, regression testing) -> test system -> acceptance test -> release the final version.
Of course, interspersed with other tests, if related to agile development can also reduce a functional test, but basically, the testing process in accordance with the above said, it will not be pass out. Of course, more stringent company, when the release version may have a trial version, the official version of the points, look at this specific project needs.
Testing requirements analysis phase: reading needs, understand the needs, mainly learning the business, demand analysis point, involved in needs assessment meeting
Test the planning stage: The main task is to write the test program, refer to the software requirements specification, project master plan, including the test range (from requirements documents), scheduling, allocation of human and material resources, the development of the overall test strategy. Risk assessment and measures to avoid a making.
Test design phase: The main is to write test cases, will make reference to the requirements document (prototype drawing), outline design, detailed design documents, use cases will be reviewed after the completion of the preparation.
Test execution phase: build environment, perform smoke testing (pre) - and then into the formal testing, bug management until the end of the test
Testing and evaluation stages: a test report to confirm whether the on-line test
In fact, many times, companies do not need such a complicated process, especially small companies, in order agile development may reduce the number of steps, I would not have met the performance test, only a test on the company on the line, of course, to do so, risks are also high, we can not guarantee the quality. The interviewer would like to see you have this process specifications. Share a little testing technology every day, like it concerns the author completely free VX public's King Brother No. automated test public update earlier and more comprehensive.