When you teach yourself to test and try to write test cases from flowcharts, you really need some methods and strategies to ensure the order and enforceability of test cases. Here are some steps and suggestions to help you write a well-organized test case according to the flowchart:

Understand the flow chart:

First of all, you need to fully understand the business process or system operation described in the flowchart.

Pay attention to the key nodes, decision points, inputs and outputs in the flowchart.

Determine the test objectives:

Before you start writing test cases, be clear about your test objectives. This helps you decide which scenes and paths need to be covered.

Using equivalence class division method:

Equivalence class division method is an effective test case design method. It can help you to classify input data into valid equivalence classes and invalid equivalence classes.

For each input point in the flow chart, consider its possible input values and determine which values belong to the valid equivalence class and which values belong to the invalid equivalence class.

Applying the boundary value method:

Boundary value method focuses on the boundary value of input data. In the flowchart, these boundary values may correspond to some specific conditions or thresholds.

Make sure that your test cases cover these boundary values, as well as values slightly above or below these boundaries.

Use scenario method:

Scenario method is a process determined by the path described by use case. In the flow chart, each path can be regarded as a scene.

Write one or more test cases for each scenario to ensure that all possible branches and decision points are covered.

Write a test case:

Test case number

Test case name

Test objective or description

Preconditions (if required)

input data

Expected result

Actual results (to be filled in after the test)

Organize your test cases in tabular form, and each test case should contain the following information:

For complex scenarios or paths, you may need to write multiple test cases to cover all possible situations.

Execute test cases:

Perform tests according to the order in the test case table and record the actual results.

If the actual result does not match the expected result, it will be recorded as a defect or problem.

Write a test report:

According to the test results, write the test report, summarize the test implementation, find defects and problems, and propose improvement measures.

Continuous learning and improvement:

Review your testing process and methods and find out where you can improve.

Keep learning and exploring new testing techniques and tools to improve your testing efficiency and accuracy.

Finally, remember that testing is an iterative process. With your knowledge and experience of the system, you may find it necessary to add or modify some test cases to better cover the functions and performance of the system.