We should do an overall system testing of the software after it is done. It sounds not a big deal, but the fact is not like that. Testers are required to be familiar with the software, all the functions of the system and have a complete testing method. Here are some of my experiences of testing to share with you.
1. Have a Full Grasp of the Business Process before Testing
Firstly, before the system testing, we should be clear about the business process of the system, in other words, we have to know the order of all the businesses. Only if we know the order, our testing data can flow freely in the ERP system. Or an overall testing cannot be conducted. Secondly, we also should be familiar with the process of every business and the roles involved. A relatively complicated business always has many detailed process. When you have handled the business entirely, you are able to do the test. For example, in the process of order management, the salesman creates an order which requires review of supervisors, and then the order can be carried out and closed.
2. Be Clear about the Functions of the ERP System Corresponding to the Business Process
After we have an overall understanding of the business, we should divide the business into small parts, and match the modules of ERP and the different parts of business. Only if we have done this, it is possible to do an overall testing to the ERP system.
3. Concentrate the Test on the System Functions and Testing Methods
According to the current process and role of the business, our test should concentrate on the ERP sub-system. Here are some methods for us to do an overall test to the greatest extent.
1) Do the Testing in the normal scene
According to the business process, we can test the system in a normal order, with the right data. Then we check whether the results turn out as we have expected. If yes, it means that the current system modules conform to the logic of business; if not, we can deduce that the system has a problem, and we have to record the errors in the bug reports and hand them to the development department as soon as possible.
2) Test in an Abnormal Scene
According to the business process, we can input some abnormal testing results into the system to see which abnormal results are pointed out by the system and whether the system makes the right judgment. If yes, it means the system takes the abnormal conditions into account, or the system may ignore the abnormal condition. We have to tell the development department to take the abnormal conditions into consideration.
3) Process Special Data
According to the business process, input some edge training data, null value and other special characters, to see if the system recognizes if the data conforms to the requirement. If not, it means that the system does not take the data range and entry requirements into account, so we have to inform the development department to add relevant data range and requirements.
4. Present the Bug Report
Through the previous tests, we have to present the bugs in the bug report and send the report to the corresponding developers, so that the errors can be eliminated at one time. The contents of a bug report usually contain the number of the error, date of finding, name of the sub-system, name of the level 2 module and the level 3 module, page, description of the error, founder, whether to modify the status, modifier’s opinion, modifier, date of modifying, confirmer, the date of confirming.
5. Go Back to Test
After the bugs are all eliminated, we should renew the ERP system, and then do the second test to make sure that the wrong information is all corrected.
