Software Test Engineer for recent college out of me is a familiar and unfamiliar vocabulary, is white class. Chose this job in mind is that a good test to use, even without any experience in testing, that's a little more difficult than the development of small, pressure is not so big. Before formal testing, only testing experience is the school each semester, "forcing" our own system, its own test whether there is bug, or do not give credit. Think about that time may be hard, but get little a technology for faster and more systematic understanding. So I think the test is a need for more empirical work. This will be a more perfect system detects whether the project in question, the question is where is. After working for a month, according to their test program probably wrote a manual test step-outs, as shown below (think of what to write, if there is something wrong, please enlighten, learn together)
White test test step-outs record (hand measurement, functional test)
First, some of the features of the test, provided that: There is no mission statement and description. Do not understand the project (old project).
1, no mission statement, no explanation and so on. Please Developers explain the process again, because it is old, so do not understand the whole process.
2. The developer said process, consider whether the normal logic. Depending on the project, consider the test cases, writing test cases, the test results to see whether the test case. Finally, test feedback.
3. Note: When testing the database must be understood that the data must be written in, which is the most basic.
Second, test the complete project.
1 What, in time to test the new system, we must first carefully read the instructions and develop the mission statement, understand the need to test the function of
4, a test to know the correspondence between the database, the data table.
5, test flow according to the actual changes :( test test)
1. "Log" pay attention to whether there are registration, login, if there are the conditions shown after registration, login, registration error, you are prompted to correct.
2. Check that each page has a layout unreasonable (do not meet the normal logic)
3. Follow the instructions and operating procedures mission statement development, checking whether the correct and reasonable.
4. Check whether each field corresponds to the text box, whether to add the data correctly.
5. If there is an error on down and shot, back to the developers.
6. Developer changed after the package provided by the cloth test.
7. Note that the test is not resolved sure to write down, in order to avoid future problems with the system say that the test did not test out of the question.
8. Precautions sent packing line (all the documents provided by the developer to be packaged, recording time, test the remaining issues, remember to complete the contract screenshots, recording status at the time of the contract appears) (now the inauguration of the company a bit special, skip see next item)
9. query, on the second page have to test was successful.
10. New, whether it is the latest in the first row, press the reverse order. (New data is written to the database)
I remember in school when the teacher said the word "come out to mix sooner or later have to repay." I say that now, even after learning in school, it think it is not enough, there will be more challenges waiting for you every day. When testers for me the most is really the best understanding of testers is a project of the people, and when the test is really sometimes have to be versatile swordsmen, who will be the best test is developed. Now there yet there is a good distance away, in the first phase of testing personnel, from the bigwigs of the realm, distant but not inaccessible. Are a daily supplement to their knowledge of the lingua franca of all kinds, even now I do not have access will use later on, saying the technology more than body ah! ! ! The first chapter, so much nonsense, after filling it, long way to go yet ......