Find answers to your thoughts

In nearly 3 years of testing work, has been to keep a curious heart, and constantly try new test direction, manual, Automation, white box, performance, operation, in this to their own previous testing work to summarize.

The hands-on projects include Web sites, TV channels, mobile apps, community terminals, banking and financial systems, not into the scale Test team, but the process is roughly the same, participate in requirements review-write test plans-write test cases-Test case reviews (product, development, Project manager)--a single module completes the round test (every Test rounds, carries out the test conclusion)--After several rounds of testing no functional problem (equivalent to the beta)-out of the test report-the project is on-line.

Demand review to publish their own views on demand products, use case review to test-centric, the need for clear thinking.

Use case design

A good test case is to cover more functional points with the appropriate use case. The simple function writes hundreds of use cases, writes the finer, the request changes, the use case cannot use again. Use cases are too coarse to write, and some function points cannot be overwritten. Ideas are comprehensive and use cases are flexible. Spend more time studying the business and needs being measured. Learn more about other people's use cases.

Flexible Use Cases

Expected results will write "give the corresponding hint" "match input content" and other vague expected results. As for the development of the specific how to design is his thing. As long as it is reasonable and does not produce ambiguity, make it easy for the user to understand the design. If there is a clear requirement in the product requirements, be sure to write clearly.

Check the document

The most tedious thing for testers is a project to write many documents, test plan documents, test case documents, test reports, test report documents, acceptance plan documents, and so on, to examine the document carefully.

Testing the technology to accumulate

According to my current work, need to be familiar with the structure of the system, familiar with the development of the language, familiar with the database, in addition to measuring the interface test function, you can check the database, whether the data is stored successfully, or modify the database data to view the previous effect. Simulate business processes by modifying database table data.

In the foreground interface operation, to check the server log, whether there is an error message. Sometimes it is possible to locate or determine the cause of the problem through server logs.

Multi-use page analysis or grab Bag tool, for example, button click Invalid, then use the Debug tool to view the properties of this button on the page. Use the grab Bag tool to look at the request and response. In short, try to dissect the tested system during the test.

Test Discovery Issues

The most exciting moment for testers is to find bugs. When you find a bug, don't rush to report to the defect management system or tell the developer. First determine the repro step. Try a different system and try again with a different browser. Maybe you forgot to clean up the browser cache causing a problem. Well, it's best to try to locate and parse the source of the bug.

The 2nd I would like to say is, to find a vague problem, should try to stand in multiple angles to look at the problem, standing in the user's perspective to consider the impact of the problem. Look at the seriousness of this problem and the cost of repairing it in the development perspective. Explain to the developer how this problem affects the user. This will develop a harmonious relationship.

Test the knowledge points to be mastered

1. Understanding the nature of testing

2. To learn is software knowledge, testing is for software services, software engineering, programming language, architecture, network, all with the development of knowledge, you have to learn, here to learn a lot of things, do not require depth but the breadth of requirements. When we are in need of review, sometimes developers will talk about technology implementation, function logic, internal processing mechanism, architecture level and so on, if you do not understand that many "outsider" ah, of course, these knowledge imperceptibly effect your test behavior, the depth of understanding of the system and find the depth of the problem.

Do not hesitate which technology is studious, which technology has the future, which technology salary is high. Whether you learn or not, the technology is there, your skill level does not increase or decrease. Of course, can not always hard study, learn a period of time should stop to summarize and think. What route do I have to take? What skills are lacking in the route I am taking? What else I need to strengthen. Of course, we should also pay attention to the future technology trends.

Responsibility determines value

Find answers to your thoughts