Financial Service Platform project test work summary

With the hard work of our colleagues in the settlement department, and the hard work of the developers of nantian company, with the careful cooperation of our colleagues in the Development Department, the online payment and batch debit services of the new financial service platform successfully passed the business acceptance test.
The test work of the new financial service platform is summarized as follows.
The following are the main reasons for better performance:
1. Measure System functions carefully and thoroughly. On the one hand, it is because the launch of the transaction is relatively small, the time and manpower arrangements are relatively adequate; on the other hand, it is also because of the hard work of testers and the indomitable spirit of the problems found in the test. Although there are not many transactions, online payment transactions are cross-line real-time transactions, which require high system performance and risk control. In addition to general business processes, perform a detailed simulation test on all possible exceptions in the business process, and track and solve existing problems.
2. The progress in the testing process is well controlled. What tasks are completed in each stage, accurate to what is done in each day, and preparations need to be made in advance, this ensures that the test progress is executed according to the test plan, and even the progress in some test stages is earlier than the time specified by the People's Bank.
Iii. Make a detailed record of every problem found during the testing process. Although the workload for maintaining the problem sheet by the testing team and the development team is increased, however, it plays a role in tracking the handling status of each problem record, ensuring that the problem is solved on time, and preventing omission of the problem.

However, we have not done enough in some aspects during this test.
1. During the test, the test team is responsible for identifying the problem. The Development Team is responsible for solving the problem, and I participated as a member of the project management department, my main task is to solve the coordination problem. However, due to my lack of in-depth understanding of our social security system, I have not done enough in coordination. Most of the problems found during the test are true, but some are also "pseudo problems", that is, problems caused by incorrect operations by business personnel or other non-system factors, it is not within the scope solved by the development team. Several times I mistakenly think of some "pseudo problems" as real problems, wasting the time of the development team. Even if it is a real problem, the project team should carefully analyze the problem, determine the cause of the problem, and then submit it to the corresponding development team. I have not been accurate enough to handle a few issues. I did not submit the issue to the corresponding developers, slowing down the problem resolution process.
Ii. nonstandard Test Cases
The test cases of business tests are prepared by the Business testers according to their needs. Although the key points of the tests are accurate, the preparation of the test cases is not very standardized. Each test case must have a unique number used to associate the test case with the test problem. When solving the problem, the developer can find the corresponding test case by serial number to reproduce the problem found during the test, so that the developer can locate the problem easily.
3. No project documentation
A major challenge during the testing process is that nantian did not provide the project development documentation, which made it difficult to locate the problems during the testing process. In the project process, the coding phase is directly entered from the business demand phase, and the design process is not recorded in the form of documents, resulting in non-transparency in the design phase, and the software quality is not guaranteed, testing problems are hard to trace, so that the risks of the system are concentrated on one or two developers.

In the future, we will try to use professional defect tracking software to manage the problems we found during the test and further ensure the quality of our system. However, because the improvement of the test process will affect the work habits of developers and test team colleagues, it is estimated that there will be some resistance to the implementation, so standardizing the project process will be a step-by-step process.