Module function Point test method template

XXX function Point test method The purpose of Function point expectation:

1, the main objective: xxxxx (describe this function point is developed for what purpose, that is, requirements to achieve the purpose. ）

<?xml:namespace prefix = o ns = "Urn:schemas-microsoft-com:office:office"/>

2. Secondary expectation Purpose: xxxxx (describes the function point in the description of the error, in various circumstances, such as adaptation. ）

second, the function point realization principle:

1, describe the function point design ideas, please refer to the requirements specification and outline design documents to write.

2. If the document is missing, ask the developer of the feature point to document it or ask the developer in detail. third, the function point realization process

1, according to the outline design document process Description to write, attach a flowchart, write on the flowchart of each step of the description information.

2. If the document is missing, ask the developer of the feature point to document it or ask the developer in detail. iv. Testing Process:

1, Environment collocation: If you need a specific environment, detailed description here.

2, the use of test tools: If you need to use the test tool in the testing process, please explain it here.

3. Test Case: Write the test case name and get path used in this test

4, testing detailed steps: Detailed description of the trigger conditions, the file name of the response, the process of the beginning of the logo, the process of the process, the process needs to monitor the debugging information, the test process changes in the document, the process of the end of the logo.

5. Test the expected results: Describe the expected results after the completion of the process, including which errors are not allowed, which errors need to be prompted, the wrong correction scheme, etc.

v. Considerations and Summary:

1, fill in the test process need to pay attention to matters. What kind of files are necessary, and what are the effects of missing?

2. Test ideas: What special use cases (boundary values, equivalence classes, error guesses, etc.) are used in the test, which may lead to problems in different environments (network anomalies, testing the function points during the implementation of other functions).

3, Summary: Test tools to use the know-how, how to write high-coverage test cases, test methods can be applied to other modules where the constraints of the input box can be applied to where. ）。

4. Test Case completion: After a round of tests, the missing test points that are found are fully complement the previous Test cases.