Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How does the bank make sure your purse is safe? Find out about the bank test you don't know.

2025-03-04 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >

Share

Shulou(Shulou.com)06/01 Report--

As a bank tester who has been employed for two years, although he is still in the growth stage, he can also sum up some experience based on his work experience to help newcomers avoid lightning. Next, I will summarize it into eight points and share it with you.

1. Participate in requirements review

Business, development, and testing seem to be different individuals, but the actual work is closely related. Testers often get the business requirements statement at the development stage and begin to write test cases, which will undoubtedly reduce the efficiency of testing. Requirements review helps to quickly and fully understand customer requirements, it will save follow-up testers time to understand business requirements, and testing key points and difficulties can take this opportunity to clarify at the meeting, after discussion to find a solution.

two。 Write test cases with the help of business flowchart

For some complex requirements, because there are many branch paths, it is easy to ignore individual cases in testing. At this time, try to draw the business flow chart according to the business requirements, or ask the developer whether he or she has referred to the relevant business flow chart when coding. The business flow chart can intuitively and clearly show the situation of each branch path, and effectively avoid the phenomenon that the test case is not comprehensive.

For example, when I was testing the optimization of transactions related to the freezing of public accounts, I drew a very complex business flow chart based on the business requirements of just a few lines. The following figure is a simple version, which focuses on the business logic of partial freezing forced deduction to divide branches, and the relevant formulas and numbers are replaced by letters. For such requirements, it is difficult to design a comprehensive and correct test case without drawing or tabulating. However, after discussing with business personnel and developers and determining the detailed business flow chart, there will naturally be no omissions in the writing of test cases. Therefore, for the business requirements of multi-branches, we should be good at drawing and use charts to clarify the test ideas.

Freezing buckle flow chart

3. Business correlation system analysis

In the field of testing, insufficient analysis of related systems is one of the important reasons for changes. The system interface of the server side has changed, and the function of the relevant consumer system calling the interface should be adjusted according to the situation, or full regression. Because cross-system calls often involve multiple developers, the solution to each other's system is not enough, and the correlation analysis should be particularly rigorous.

4. Complete business scenario

Business processes often form a closed loop, opening accounts-enabling-canceling accounts, freezing-re-freezing-thawing, signing-maintenance-termination, so the business scenario should be as complete as possible. For example, the logic of the expense account may be different at design time. When opening an account, the customer number of the new account and the customer number of the transferred account are not judged, but the customer number is required to be the same when paying and closing the account. Therefore, there is a risk that an account can be opened but not closed and other operations can be carried out. Therefore, in the case design, although the transformation point is to open an account transaction or sign a contract transaction, but we should try to test a complete business process.

5. Date

Date is a very important factor in testing, maybe the transaction that can be done on the same day, change the accounting date or change the transaction date will fail. For example, when testing the multi-level book balance adjustment, if the original transaction date is the current accounting date, the transaction information is correct, and the original transaction date is less than the current accounting date, then the cashier's multi-level account number is incorrect because different transaction dates correspond to different branches of the program. Therefore, when designing a case, we should fully consider the impact of time factors on the transaction, and analyze whether it is necessary to design various date values.

6. Cache data

When there are strict requirements for test data, such as terrorism-related information, attention should be paid to the impact of cached data. For example, if you first enter a set of valid data, submit it, and terminate the transaction in the middle of the transaction, the transaction information will not be emptied, then it will be modified to invalid test data, and then it will be submitted, which is contrary to the business requirements. Therefore, when there are restrictions on input, you should ensure that the cached data is emptied or updated in a timely manner.

7. Test data type

The variety of test data should be rich, for example, if this transformation involves temporary accounts that have expired, then temporary households that have not expired, basic households that have expired, general households that have expired, special users who have expired, registered capital verification households, foreign exchange accounts that have expired, and so on, should be verified. Often the defects occur on the associated elements rather than the transformation points themselves, because developers only unit test the transformation points while coding, while the associated elements are easy to be ignored.

8. Voucher return order

The voucher return order must be clear and intuitive, so you need to check the display of the voucher return order after the success of the transaction. It is important to check whether the transaction information replaced by ellipsis is important information, such as amount, account number, etc., as well as whether the seal will cover some important information and whether there is enough space for the customer's signature.

Add me VX:atstudyIT to reply the keyword "test" to get limited software test learning materials.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Network Security

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report