How do you test fintech quickly without sacrificing quality?

I agree, but I think it is also important to talk to business stakeholders to gain further insights into what is valuable to add to the test strategy.

Testing scope definition can either be provided by someone who has seen the growth of application and understands what's important for users. Now this can either by done by actual users, business people or product owner (but note PO who is new to software may not be the best person). Once understanding the important factors for each feature and its impact on system as well users, we can start with further testing procedures.

In addition, the legal field in fintech is very complex. It is recommended to hire people from the legal field with specialization in the countries where the company wishes to work or in the countries with which the state wishes to work.

Automating the stuff which is stable is the way to move forward. Now let's take an example, Smoke testing is the most easiest way to start with automation. Because most the crucial functionality can be automated which helps provides whether application is stable or not. Whereas if we start with automation for parts like exploratory testing, regression testing it becomes complex because, choosing what to automate & what not to requires critical understanding of the system.

In addition to that, automated testing gives you also more additional time to do manual testing during one test cycle and gives you opportunity to improve test coverage of non-automated tests.

automation is always crucial part for making an product especially testing for that. selenium and many other lib can provide you running same test scenario as manual as well as it reduce human error and provide a proper documentation of test result. It provide reproducibility and same results for given test scenario by avoiding human bias for given feature while doing manual testing.

Identifying the scope of Automated testing is very crucial to avoid effort in rework or maintenance of scripts. The stable functionalities or scenarios should be automated first and the functionality which is expected to change in future should be handled using Manual Testing. In this way, we will achieve sufficient Test coverage and ensure that critical scenarios are checked manually covered during Testing. Fintech most times involves calculation of amounts, hence using automated tests is a safest way to verify the calculations to avoid any human errors on manual Testing.

It is recommended to make simulated environments especially for the stage of transferring the funds so as not to do tests on real money.

The term is not precise enough. The agile part talks about the "quick" way of working and rapid code release. Using devops talks about processes of integration between parts, CI-CD that will help things run faster and more stable and more...

In the field of tests: Testing in a cloud environment allows us the option to test in a large number of situations and in addition does not take up local resources but you have to pay attention to its cost. API testing will be appropriate for some things - depending on what your fintech product does. You may only be able to use the API and you may need to check for UI environments. It all depends on the product.

And for that there are other tools on the market that will help us analyze situations according to our tests. And of course there are data teams that some of these tests are under their responsibility.

As a QA working for the first time in a fintech company was quite challenging, with a lack of resources and time to maintain quality. I had to overwork a bit initially, but I had a good manager who shared the workload with me and helped me redefine the test cases to test minimum test cases with maximum quality.

Understand the purpose of the software from the End-user perspective. Act as a bridge between technology solutions and business demands. Always think and talk based on impacts.

Automating the testing process can help streamline testing, reduce testing time, and improve the accuracy of test results. Automating the tasks frees up testers’ time to focus on more critical aspects of the app.

1. Refinement Sessions - improving the understanding of requirements before coding. 2. Code Quality - using tools like Sonar qube to maximize the development effort. 3. Test Quality - Redundant test scenarios can be automated so effort is managed efficiently by parallel Manual Test execution of critical scenarios and basic sanity checks. 4. Business Demos - giving them the understanding of the implementation of the requirement.