Team building path (3) -- Test Management

Originally, the Group Company had a test management system, but it was useless.

One of the reasons is that it is inconvenient to use. The website of the test management system is built on the Internet. For security reasons, the Internet and Intranet are physically isolated from each other. You must switch the network cable to switch the network.

The second reason is that the test management system has not been established. The local software developed by Guangdong company has always been commissioned by a specialized testing department of the Group headquarters to come to the Guangdong branch for testing. However, such professional testers will only appear when the software development has been basically completed, after about a month, the customer will go home without tracking the project acceptance. Therefore, we can imagine the test results. First, although the testers are very professional, they have limited understanding of our software and basically do not know the specific business. They can only perform "interface and operation" tests. Second, tests have never been carried out throughout software development. They only perform the "pre-Acceptance Test" step. Therefore, we basically did not rely on the testing staff at the headquarters, but did rely on the development staff to perform self-testing or cross-testing on their own. Instead, we were able to identify more problems.

In fact, this issue has been raised by many colleagues. The above mentioned three senior software engineers, each of whom submitted their suggestions on improving this issue shortly after they joined the company, however, it was not accepted for various reasons. Therefore, this time I proposed to create our own Test Management System, which naturally received a positive response from everyone.

This test management system must be web-based and run in the LAN and can be used with the email server.

Based on your previous experience, two systems are selected as candidate references. One is test driven and the other is bugfree. The advantage of TD is that it runs fast and comes with snapshot and other very useful small functions, but it is complicated to use. The advantage of bugfree is that it is open-source and simple. The most important thing is that the process can be referred to Microsoft, it feels more reasonable than TD. For example, there are 6 bug actions in TD: new, open, reject, solve, close, reopen, but in fact some bugs cannot use these actions, for example, if a bug exists, but can only be solved in the next version, TD cannot handle such a situation. Bugfree has actions such as by design and postpone to solve these problems. Therefore, we finally chose bugfree 1.0.

The installation is very simple. After you download greenamp and bugfree from the website, decompress greenamp, run Apache service, decompress bugfree, run install. php to create a database structure, and then you can log on and use it.

The test management system has been initially established and requires the cooperation of rules and regulations. Let's work it out in a few days.