After working in a software company for five years as a test manager, he moved to a bank to do software testing . In just two months, he had a preliminary understanding of bank testing, summarized and recorded it, deepened his personal understanding, and shared it with everyone.
As everyone's financial advisor, the bank is very sensitive to money. Frequent or even occasional software failures will damage the confidence of customers. If there is a hacker attack and personal property is threatened, the bank will inevitably suffer losses. Therefore, banks have very high requirements for software quality, which is also a major feature of bank software testing. Next, let's talk about the bank's software testing from multiple angles.
business and technical aspects
Since a lot of content is afraid of involving bank commercial secrets, here is a brief chat.
The IBM server technology that the bank mainly uses , I have never been in touch with DB2, and I am used to using Oracle . It took a long time to adapt to DB2, which has no front-end graphical interface at all. But the principle of the database is the same, as long as the path is clarified, the query and screening of the required data can also be completed. So when you encounter Db2, you can calm down and study the prompts on its interface, touch every function, and gradually become familiar with it.
The bank's system is quite complicated, and the bank-related business knowledge I have is limited to personal deposits and withdrawals and online banking payments. The content I tested is a very large business system, most of which cannot be directly seen, and can only be understood by myself. For example, if I want to test a certain business, I find that what I operate is not the user interface at all, but the interface data submission interface provided by the development. For this kind of situation, there are a lot of banks, so we use a lot of simulators. But for these complex software tests without visible user interface, I personally have a very good method, which is to start from here by sorting out business processes and data processes, and slowly expand my business knowledge through test cases . The function points that each type of business process needs to cover, and finally sort out all the scenarios and checkpoints that this business process needs to cover.
Also, very helpful is the technical documentation. As long as I have time, I will read relevant design documents, including business requirements, overall architecture design, database design, test plans, test requirements, summary documents compiled by experts, etc. (there are many test cases, and the projects we tested are Tens of thousands, so no recommendation), through these contents, my knowledge will be greatly expanded, and at the same time, I can ask experts for advice when I don’t understand. In this way, a network of interpersonal relationships has also been established. Coupled with frequent questions, everyone's recognition of me has also increased. I guess it's also a way to sell yourself. On the one hand, I have acquired knowledge, and on the other hand, I have established a very good relationship with everyone, killing two birds with one stone!
process and personnel
Second, talk about management processes and people. The bank I work in divides software testing into two parts, ST testing and UAT testing. I belong to ST functional testing, so this article will also focus on this. ST's internal management process is based on a very traditional test management method, making a test plan --> analyzing test requirements --> writing test cases --> executing tests (including executing test cases and bug analysis) --> summarizing and writing tests Report. The whole process is reviewed and checked by senior testers, and it is required to pass the review. The test is executed in multiple rounds. Generally, there are two rounds of ST and two rounds of UAT testing. After each round is completed, a cross-test will be carried out. The test environment is in charge of a special person. During the test process, the development will frequently fix problems and type the version into the test environment (the term here seems to be called rewinding). The test executives generally only verify after the bug is fixed, and do not pay much attention to the version of the test environment at other times.
The test management is divided into two lines. Taking our existing project as an example, there are more than 50 testers. A team leader A responsible for personnel management manages all testers, including personnel coordination and performance tracking. A B responsible for technical management is responsible for formulating test plans, organizing analysis of test requirements and designing test cases. In addition, under the banners of A and B, there are multiple groups, there is a test design group a, five test execution groups b, c, d, e, f, and each of these six groups has more than one person, and each group Have a group leader. The team leaders of groups b, c, d, e, and f are responsible for collecting the problems that the team members cannot judge every day, and helping to solve them. For those that cannot be solved in the group, they need to seek help from other experts or developers. I am the test executive o(∩_∩)o of a certain execution group. Manager A requires the executives of the test execution group to execute no less than *0 use cases every day. The first news in the daily group is the amount of test execution per person per day that A statistics and publishes. The daily pursuit of test executives is to complete these tasks.
Occasionally there is still training. I participated in it twice, one for system architecture training and one for a certain part of business training. I have gained a lot, at least I know the relevant people, and I can ask them for corresponding problems. Of course, there was also unfair treatment. For example, when I went to ask for the design document of the system architecture, I was told that it was an internal document and it was not convenient to send it to me. That is to say, this is internal information and cannot be given to you who are not insiders.
In short, compared with my previous work, in pursuit of speed and low cost, acceptance is the "king". What the bank project pursues is stable function, reliable performance, and high security, and finally achieves customer trust and guarantees that the bank and personal property are completely correct. Then the entire testing process is interlocking, each process is taken very seriously, and every business process affected is covered as comprehensively as possible with rigorous logic. From this perspective, we testers should understand the entire testing process more, improve our testing level, and make continuous progress, so that we can truly achieve something in bank testing.
Banking Test Interview Questions
1. How to test online bank transfer, design a test case
2. What is the process of testing work? What are the defect states? How many ways are there to design test cases?
3. What is the classic BUG found in the project?
4. How to measure the automatic transfer of fixed deposits upon maturity?
5. What should you do after you find a bug?
6. If a BUG is found, it has nothing to do with the development itself, but involves concepts and requirements, how to solve it?
7. How do you divide the BUG level of functional testing ?
8. Execute someone else's use case, what to do if you find that the use case is wrong?
9. Have you done smoking side? What is smoke testing (theory)?
10. How long have you been working on the project, and how many use cases have you written? How many people are there in the project?
11. If you want to test a p2p loan product with a period of 6 months, how should you design the case and name the test points
12. Is your P2P online? Can I check it? How long did the project take and how long is it expected to be completed?
13. How did you measure the real-name authentication? What platform did you obtain the information from?
14. Is real-name authentication required for registration?
15. Do you also test the background management of P2P? Where is the personal Zhima credit obtained?
16. If you want to test the deletion of users in the background, it is the case of a delete button behind the user name. What test cases can be written?
17. If JD had a shopping webpage for you, how would you test it? What main functions would you test?
18. How many rounds of P2P function testing do you usually do?
19. Do more than a dozen developers go to the meeting every time you hold a meeting to discuss?
20. Are you familiar with database? Do you usually use the database a lot?
21. Is the database used often?
22. What command does 1inux use to view files and processes?
23. Who provided the test environment for your test? 1Inux how to build a test environment?
24. What should you do if the leader assigns you overloaded tasks and the leader overestimates your ability?
25. What should you do if there is a problem with your work due to your mistake?
26. Given a module test, how can you complete it efficiently in only one week?
27. If you are given an app test project with no requirements, how should you test it?
28. If you have a disagreement with the developer, how do you deal with it?
29. If the use case of your team leader is wrong, but he thinks it is correct, how do you deal with it?
30. You are responsible for both function and performance. How do you do it?
31. The language used in our company's automated testing is Java . I will meet you in advance. How can it be so fine without a watermark?
32. How were the previous projects managed?
33. How many use cases need to be executed per day in previous projects
34. Did you do all regression testing when you did it?
35. How do you ensure use case coverage? Make sure not to repeat?
36. How are your cases reviewed?
37. What is a view?
38. The database looks up two tables
39. I have worked very hard, but still have not completed the tasks assigned by my superiors, what should I do?
at last
The threshold for software testing in the financial industry is high. In addition to understanding software testing knowledge, there are requirements for your business ability and banking and financial knowledge. Friends who want to go to banks to do software testing should work hard!
Finally: The complete software testing video tutorial below has been organized and uploaded, and friends who need it can get it by themselves [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
