What are the better test case management tools?

"I am new to a small start-up company and I want a tool that is more efficient and easier to use than Excel." I predict that many people will mention TestLink, Jira, PingCode and other platforms. One set, then people can't stand it. In order to save everyone from detours, I wrote this answer.

How to write test cases, I will not go into details here, if you want to learn "teaching test case writing by hand", I strongly recommend reading the following two articles:

"What should I do if I feel that the test case is so difficult to write"

"How to write test cases"

1. Why do the above platforms (TestLink, Jira, PingCode) all pass?

1. Product positioning does not match

The positioning of these products is for project management, and the use case management we need is just one of the small functions. Although this type of platform is rich in functions, 90% of the functions are not available, which is tasteless.

2. Poor collaboration

Most of these platforms need to be deployed locally, and everyone needs to register an account (product, R&D, etc.). In order to manage test cases, it is very difficult for us to get so many people to cooperate.

3. Poor operability

The actual experience of using this kind of software is not silky smooth, even a bit cumbersome. Using them for use case management may not be as convenient as excel.

These platforms basically use technologies and design concepts more than 10 years ago, which seem to be outdated today (as the topic owner said, some platforms have "ugly interfaces and relatively backward functions")

To sum up, we don't need heavy platforms like TestLink and Jira, but a tool as simple as excel but more efficient than excel.

However, is there really a product as simple as excel but more efficient than Excel?

2. What platform should be used as a use case management tool?

Before officially answering, ask a question: What is the third-party collaboration software used by your company? (Small start-up companies will definitely not develop their own collaboration software, so I directly ask what third-party software they use)

If you are not using one of DingTalk, Qiwei, or Feishu, but are using WeChat or even QQ to communicate, then I advise you to run away quickly. Can such a company still be called an Internet company?

If you really use one of DingTalk, Qiwei, and Feishu (Internet companies that focus on collaboration efficiency will basically use one of them), you can continue to read.

You may be using DingTalk, and then have a question: How does DingTalk manage test cases?

Don't worry, we are actually talking about a product under DingTalk - DingTalk Documentation.

The following is a detailed introduction from four aspects:

1. Use threshold
2. Function
3. Collaboration
4. Convenience

1. Use threshold

Accounts are universal. The reason why DingTalk was mentioned above is because one account can be used universally for all functions of DingTalk, including DingTalk documents (WeChat is the same for Tencent Documents, and Feishu is the same for Feishu Documents).

No need to download, it can be accessed through the DingTalk client or the webpage, and it will go away when it is used up, and it does not take up memory.

It's easy to use. It's the first time I use DingTalk documents. I don't know how to write use cases. It doesn't matter. There are ready-made templates for reference, so it's easy to get started.

2. Function

1) There are many types of documents. Some people like to use Excel to write use cases, and some people like to use brain maps to write use cases. It doesn’t matter. You can do whatever you want, and there are many templates for each document type.

2) Combined use, we have all used Excel or Xind, but the function is single, and the management of test cases is a bit powerless. DingTalk documents can solve these pain points. A document supports multiple formats, which can be used alone or in combination. Codes, brain maps, tables, flowcharts... Different types of use cases are presented in different ways, which is very easy to use.

3) Abundant tools, if you find that the interface document is missing when writing a use case and want to remind R&D to add it, you don’t need to find another R&D to communicate, just @R&D in the document, the person you @ will receive the message in DingTalk Notice; I want to use video to illustrate the expected effect of the test, -- support, I want to add some small tools -- also support, in short, it has everything you can think of.

4) For document demonstration, screen projection is required during use case review. It can be demonstrated like a PPT, and has more functions than PPT. It comes with tools such as a laser pointer, and the demonstration effect is quite good.

3. Collaboration

1) Share, the test case should be shown to others, you can share it to DingTalk chat with one click, you can also share it through pictures or emails, and you can even generate a video and share it.

2) Permissions, customizing the scope of visibility and collaboration, setting collaborators to edit test cases together, and setting the company-wide visibility when sharing to products or R&D.

4. Convenience

1) Automatically save, write and save when writing use cases, don't worry about losing content due to forgetting to save

2) Multi-terminal access, anytime, anywhere, and can be accessed through a mobile browser without a computer

3) Remote conferences, use DingTalk's conference function to initiate a use case review meeting, historical meetings and recent meetings are clear at a glance, even if you work from home, it will not be affected in the slightest

As mentioned above, using the functions of DingTalk documents is enough for use case writing, sharing, demonstration, and use case review.

Now let's go back to the question at the beginning:

As simple as Excel, but easier to use than Excel, DingTalk documents, it really does it, and fully meets the needs of test case management.

3. What should I do if there is no DingTalk document?

If there is no DingTalk, there will always be Qiwei. The Tencent documents used by Qiwei are similar to the DingTalk documents, and the following is a brief introduction.

1. Entrance

[Enterprise WeChat Client] - [Documents], you can enter Tencent Documents and log in with the Enterprise Wechat account

There are also many templates, supporting various types of documents, tables, mind maps, etc.

2. Collaboration

3. Efficiency tools

4. Authority management

The functions, use and experience of Feishu Documentation are similar to those of the above two products. They are also common to one account and directly accessible to one software, so I won’t introduce them one by one here.


転載: blog.csdn.net/JACK_SUJAVA/article/details/130584936