We'll talk about the test plan.

Haven't updated their blog for a long time. One is busy work, and the other is his own half a year to think a little fluctuation, the mood is not stable down.

Today is October 7, 2018, this month the company received a new project, this time I write a test plan.

First of all to write test plan, I do not exclude, in addition, the company currently only I a tester, advanced to good, elementary or not, the documentation and information we still have to do it. Don't save some steps because you are lazy. We must first understand the requirements, how the requirements are defined, the system is a comprehensive game platform, can be customized, extended and extended functions. It's with Java+linux.

After communicating with the product, and then yesterday drew a mind map.

Write out the test plan today, regardless of whether later on the document to arrange their own test activities, but at least, in the process of writing a plan, help yourself to get into the work early, help understand the system.

The test plan is actually a dynamic process, just like the test case. Need to later in the test activity, the regular update, timely make adjustments and additions.

I did not refer to the online template. Only in accordance with their own understanding, only a simple record of the purpose of the test activities, scope, personnel, scheduling, resource requirements, focus, difficulties, risk points, goals. and other content.

Because to give the leadership to see, so the back also added the contact method and so on.

Online test Plan template includes a lot of, what noun interpretation, references, disputes, etc., I think the test plan is a programmatic document to guide the follow-up of our testing activities, but also according to our testing activities in the future to modify, perfect. Future testing activities are estimated in advance based on this document. Let testers be aware of future testing activities.

I think testers in the latter part of the test should try to turn over the test plan document, do not work hard, so that their job is not planned, or completely only obey the Test team leader's work arrangement, so for their future growth unfavorable. After all, in the IT industry, more hands-on, and thinking will always make people grow faster. Another situation is that some test department leaders will only blind BB, a non-beating type of face. It is difficult to work under such a person.

We'll talk about the test plan.