Which is the best test management tool? Experience sharing of well-known test management tools in China

Test management tools are an integral part of the software testing process, such as: reducing human errors and omissions, saving time and cost through automated and standardized testing processes; ensuring test traceability through complete and detailed test records and reproducibility, improve the accuracy and reliability of the test; through the graphical and report-based display, the test process and results are clearer and more intuitive, which is convenient for analysis and decision-making; through the network and cloud platform, realize Cross-regional and cross-departmental test collaboration improves the collaboration and innovation capabilities of the test team...

Test management tools are an important means to improve software quality and software development efficiency, and deserve the attention and use of every software developer and software tester. If the test team encounters the following problems in test management:

• Lack of use cases and bug management specifications, the testing process is cumbersome and untraceable
• The ecology of separation between testing and development is incomplete, and it is not related to specific needs or defects in time
• It is difficult to quickly accumulate test knowledge and experience and share internally and externally
• The test execution time of a large number of existing products is long, and the result response is slow, resulting in a poor user experience
• ……

Then try   a professional test management tool such as PingCode , and you may have new discoveries. The following article will introduce in detail which problems in test management PingCode can help solve, and how to operate it.

1. 9 steps to open PingCode test management

PingCode test management supports a professional standardized testing process, helping the testing team:

• Cover the complete testing process, help users improve testing efficiency, and ensure the quality of software delivery;
• Connect requirements and development work to achieve efficient internal and external collaboration processes;
• Master the test progress, visualize the work view to overview the test progress, identify and manage risks.

Now, it's time to start the test management process. Through the following 9 steps, quickly understand PingCode test management to help your test team complete the test process efficiently and orderly. 



Step One: Create Your Test Library

1. Create a test repository

If you have the authority to create test management, you can create independent test libraries for different projects or products, and perform standardized management and long-term maintenance of all use cases.

• Enter PingCode, select "Test Management";
• In the main interface, select "+ New Test Library";
• Fill in the test library name, test library ID and test description;
• Select members for your test library;
• Finish creating.





2. Copy the test library

As we all know, there are many same or similar functions in software development. You can copy the test library to help you quickly share or backup the test library and the test cases and use case templates under the test library. For the copied test library, you can change the basic information such as "Test library name", "Test library ID", "Description", "Add members", etc., so that you can standardize the management and accumulation of use cases, and bid farewell to the repeated writing of test cases in traditional project management , Use case information sharing difficulties, become your exclusive "weapon library".

Tips: Copying the test library does not include shared use cases.





Step 2: Manage your test members and roles

Now is the time to bring your testing team members on board. PingCode  test management provides the management of test members, roles, and teams, and can set different permissions for different roles to ensure the smooth flow of test information and protect your data security.

1. Test member management

If a new member joins during the test, you can add a new member in the test library setting interface. The default configuration permission of the newly added member system is "ordinary member". Of course, you can also "set default role" in the management background, and support batch Make member role settings. 



2. Test role management

 If you need to add more roles to the test library, you can maintain roles in the  PingCode management background, such as adding test engineers, QA engineers, etc. After completing the role setting, you can enter the test management configuration center to further complete the configuration of role permissions. Currently, 33 test management permissions are supported, and the permissions related to test management include test library settings, test cases, use case reviews, test plans, Execute the use case.



3. Test team management

A test team is a group of individuals working for a common goal. You can build your test team in the PingCode management background. You can divide your team by product, or you can divide your team by project.



Step Three: Maintain Your Test Cases

1. Hierarchical classification management test module

You can classify test cases by priority, function module, etc., and you can manage test case modules in multiple levels (up to 5 levels) to achieve structured management and further refine and classify different use cases. For example: create each large functional block of the product as a use case module, and create each function point under the functional block as a sub-module, which will make the test content of the product clear and orderly. You can also add Emoji expressions to the use case module to make your testing work easier and more interesting. 



2. Maintain test cases

• Create use cases one by one

In the "Use Case" component, you can create corresponding test cases according to the function points to be tested, write use case steps, set the module to which it belongs, and use case status, type, estimated man-hours, associated requirements, maintainers, etc. At the same time, you can also continuously create multiple test cases. Article use case. In addition, by duplicating use cases, you can quickly create similar use cases and improve the efficiency of creating use cases. 



Not only can you create use cases in PingCode test management, but you can also directly create or associate test cases under the "User Story" work item in PingCode project management to describe the acceptance criteria for this work item. If you want to know how to use PingCode project management, please refer to " PingCode project management unpacking guide "



• Create a template for use cases

If you create a test case with only minor differences, you can "save as a template" the test case. When you or other team members are writing other test cases, you can directly select the template, and with a little modification, you can quickly create a new test case, which greatly saves the time for writing test cases. 



• Batch import use cases

If you already have a large number of historical test files, or if you find that manual creation is inefficient when your demand floods in, you can import test files into the use case library in batches by importing use cases, you can import by table file, or use thinking Map import (.opml format) data to reduce creation costs and quickly generate test cases. 



• Test case more operations

When you delete a test case, the execution cases in the unfinished test plan will be deleted together. You don’t have to worry about the impact on your work after deleting the test case by mistake, because the deleted test case is only hidden in the test case list, and you can use it in the test library. The recycle bin in the configuration center restores deleted test cases. 



3. Test case sharing

You can select other test libraries under the current test library to share use cases. After sharing, you can plan the use cases to the test plan of the current test library for execution, reducing the work of repeatedly writing use cases. 



4. Associated requirements

Requirements traceability and test case tracking process is cumbersome, requiring a lot of time and manpower for statistics, summarization, sorting and release, resulting in inability to quickly respond to the market and low project development efficiency. To solve this problem, you can associate requirements in test cases through the "Use Case" component, and visually view the status of requirements, the person in charge, and the deadline for completion of requirements. In addition, after associating a requirement, in the PingCode project management, all corresponding test cases will be directly displayed under the requirement. 



5. Use case version

Test cases are repeatable and time-sensitive. Although test cases can be reused, in the agile development process, test cases are often adjusted and updated due to changes in requirements to meet the requirements of later testing. Test cases that have been executed in the past can be saved as historical versions. In the version record, you can create a new version to update the test case, and briefly describe the content of this update so that you can clearly understand the differences between different versions. 



6. Custom use case properties

When you find that the fields or displayed details do not conform to the team's usage habits when creating a test case, you can customize the properties of the test case through "Configure Test Case" and configure the new and display views of the test case. You can add or create different types of attributes in the test case "Attributes and Views", including single-line text, multi-line text, numbers, dates, drop-down single selection, drop-down multiple selection, single member and multiple members, etc. Of course, you can also edit, move positions and delete existing properties. 



7. Collaboration among team members: @ follow and comment

As the division of roles becomes more and more refined, product managers, project managers, developers, testers, and front-end developers have higher and higher requirements for collaboration, and they need to have the ability to work as a team to reduce ineffective communication. On the test case details page, you can help your test team members communicate efficiently and achieve collaborative office through functions such as @members, adding attention, #mentioning work items, online discussions, and comments. 



Step 4: Review Test Cases

After you have written the test case, it cannot be used for testing directly, because there may be some missing points. Therefore, test case review is very important. Through organizational review, the test team or project team can assist in improving the availability and coverage of use cases.

1. Review plan

An efficient use case review activity requires a review plan in advance. You can create review plans of different categories or groups in the "Review" component, such as iterative review, project review, cycle review, etc. At the same time, by organizing use case review meetings and coordinating with relevant project personnel (such as product, development, etc.), a comprehensive evaluation of the content and executable of test cases is carried out.

Tips: The main work of the use case review meeting is as follows:

• Point out the unreasonable or omissions of the use case design, so as to better improve the content of the use case and improve the quality of the test case.
• Eliminate the deviation in the understanding of requirements by all parties and ensure the consistency of understanding of requirements.
• According to the suggestions of all parties at the meeting, the test cases were revised and improved, and the participants were synchronized.





2. Plan review use case scope

Once you have created a review plan, you can plan the scope of current or future review use cases by iteration, project phase, or time, etc. You can select some test cases from the test library and put them into the plan to be reviewed. The status of the newly created test case in the "Use Case" component is "Draft". When it is selected into the review plan, the status of the test case will automatically change to "In Review", and a test case can be selected into multiple review plans . 



3. Review use case content

After you review the use case steps and expected results under the use case details page, you can set the use case review results on the review use case details page, and you can also give review opinions on the current use case. 



4. Use Case Review History

A test case can be planned into different review plans for multiple rounds of reviews. After the review, the test case details page will record the review results under different review plans. 



Step Five: Develop and Execute a Test Plan

1. Planning Test Plan Categories

You can use test plan categories to help you organize test plans into logical groups. Later, when viewing a list of all test plans, you can sort, search, and group test plans in the list. You can also add Emoji expressions to the plan category to make your testing work easier and more interesting. 



2. Planning the test plan

• Create a test plan

After the use cases are maintained, you can complete a functional test through the test plan. For which functions you need to test, use the test plan to plan the use cases corresponding to the functions to be tested. The establishment of the test plan depends on Process for each team:

• You can associate test plans with iterations, and the planned iterative development functions correspond to test cases, and then test according to the test cases;
• You can associate the test plan with the release version, and test according to the release version range.

Tips: After associating the project, you can submit the defects found during the execution of the use case, and the created defects will then flow to the "defect" component under project management, which is convenient for developers to locate and process





• planning use case

When you have created a test plan, you can plan current or future test cases according to iteration, project phase or time etc. You can select a part of test cases from modules or shared use cases and put them into the current test plan. The default status of the execution results of the selected test cases in the "Execution Case" component is "Untested". At the same time, you can Change your execution results, and a test case can be selected into multiple test plans. 



3. Execute the test plan

After you plan the test cases for the test plan, the tester will execute the test according to the test cases, confirm whether the actual value of the test process meets the expected value of the use case, and fill in the test results, such as pass/block/fail, etc. At the same time, you can also add result attachments (files generated during execution, such as script txt/pictures, etc.). If you find a defect during test execution, you can easily associate a "defect" or create a "new defect", and you can view all related defects on the test case details page. 



Step 6: Raise bugs and track defects

1. One-click bug submission

When you find a defect in the execution use case, you can immediately raise the bug in the execution use case with one click; not only that, when the developer finds a defect in a certain requirement of project management, you can also raise the bug with one click, so that the developer can quickly locate it Bugs and fixes in time. 





2. Two-way correlation between test and requirements

When your test case is associated with the requirement, when the execution of the test case fails and a defect is submitted, the defect will be associated with this test, and the defect will be automatically synchronized to the corresponding project/user story. It can be traced so that defect tasks can be efficiently transferred between the testing and R&D teams. If you want to know how to use PingCode project management, see "PingCode project management unboxing guide" for details. 



3. Track defects

In the test plan you can centrally manage the submitted defects. For example, there may be repeated submissions of the same bug, and testers or defect managers can associate the same bug to facilitate bug repair and tracking; you can also track the status of test cases, test plans, and review plans through Flow automation rules Whether to maintain consistency. If you want to learn how to use PingCode automation management, see "PingCode Automation Management Unboxing Guide" for details.



Step Seven: Generate Test Report

1. Generate test report

Execution of all test cases means the completion of a test plan. A complete test report will be automatically generated for this test plan, providing statistical information such as test progress, pass rate, execution result distribution, defect regression distribution, and daily test times. Of course, you can also customize the content of the test report. According to the test report, you can analyze the test process, quickly find problems, and facilitate continuous improvement in future work.

• Example of test report content: The distribution of execution results is one of the components of the test report. Visualize test quality by displaying test case execution in a pie chart.





2. Test report sharing

If you need to quote the content of the test report, continue to enrich the test report, or share it with other members, you can quickly view, export, and print the test report to share your test report. 



Step 8: Connect to automated testing tools

Automated testing replaces repetitive manual testing, enables frequent validation and provides quick feedback. PingCode has powerful expansion capabilities, you can integrate and dock your automated testing tools through the  Rest API  standard provided by PingCode test management. Through docking, you can realize the automatic creation, update and deletion of test cases and test plans, and synchronize the results of automated test execution. At the same time, you can complete the association between automated testing tools and work items in PingCode project management, such as associating user stories and defects, and realize the whole process management from project to automated testing. If you want to know about Rest API, please refer to " PingCode Official Website " for details.

Step 9: Measurement and management of test process data

Through the measurement and management of process data, test management can create value faster. Through PingCode test management, the data generated by the test team during the test implementation process is automatically collected and counted, such as more than ten visual reports such as test case activities, test case planning and analysis, execution result division, etc., to help the test team measure R&D in all aspects performance and make R&D decisions.

• Example of test report content: Test case activity is one of the most commonly used reports for test management. The use case activity line chart helps the team track the number of test case-related activities in the test library over a period of time, and can visually view the activity trend of test cases.

PingCode performance measurement has richer test reports. If you want to know how to use PingCode performance measurement management, please refer to "PingCode Performance Measurement Management Unboxing Guide" for details. 



2. Introduce the PingCode test management tool to the team

After completing the above content, I believe you   already have some understanding of PingCode test management. If you want to know whether it is applicable to your team, then we recommend that you start a small-scale trial in the team and listen to the voice of the team before making a judgment .

The following will summarize the PingCode test management features mentioned in the article:

• Positioning: PingCode test management covers the whole process of testing, including test case design, test planning, test execution and defect tracking, and improves the quality and efficiency of team delivery through visual quality reports, and finally forms a closed loop from requirements to testing phase. At the same time, through sharing, templates and other capabilities, test cases are extended to each group, reducing duplication of work.

• ability:
  • Establish a process closed loop: complete coverage of requirements understanding, use case maintenance and review, plan formulation and execution, automatic report generation process, forming a process, collaboration and improvement closed loop
  • Improve delivery quality: reduce repetitive actions, speed up delivery, and improve quality by tracking the entire testing process, one-click bug reporting, and quality assessment reports
  • Efficient collaboration in development and testing: associate projects, requirements, defects, and iterations, use cases can be reused, shared, and commented at any time, fast feedback, and more efficient internal and external team collaboration
  • Easy to use and quick to configure: no plug-ins required, interactive personalized configuration, easy to use, good operating experience, covering more business scenarios
  • Data connection: It can communicate with other product data such as PingCode sub-product project management, knowledge management, performance measurement and automation, and code hosting and CI/CD.
• Security: PingCode test management strictly follows relevant data security policies, and has international information security system certification, data encryption and backup, account protection and other measures, which can comprehensively guarantee the information security of your organization.

• Deployment: PingCode test management supports a variety of deployment methods, including public cloud, private cloud and local deployment; among them, the SaaS version can purchase accounts on demand, and the professional team provides operation and maintenance guarantee services. The bi-weekly version iteration is more lightweight and low-cost , Easy maintenance.

• Service: PingCode test management is serving various teams of many first-line enterprises. PingCode has the experience and ability to serve tens of thousands of members. In addition to better understanding of domestic production and research models, it also has more complete, timely and effective Customer service system.