Testing investment for financial trading systems far exceeds that of other systems, with repetitive and cumbersome testing steps yielding too little value. As projects and personnel change, uncontrollable factors are inevitably introduced; a common scenario involves modifying a field in interface A, which unexpectedly impacts the results of interface B. With each version release, risks accumulate.

Theoretical knowledge

• Please provide the Chinese text you want me to translate. I am ready when you are!

The ROI of an automated test case = (Manual Execution Time) * (Number of Runs) / (Development Cost + Maintenance Cost)

• Please provide the Chinese text you want me to translate. I am ready when you are!

Focus on automating tests for frequently used, stable features – this yields the greatest return

• Please provide the Chinese text you want me to translate. I am ready when you are!

It’s not suitable now, as it’s like fetching water from afar to quench a thirst. Automation is a long-term benefit model. The project is already live and entering a stable release cycle; this is the best time for it.

Framework Selection

Being assigned an automation testing task without relevant practical experience often leads to this: opening a search engine, looking for tools and frameworks compatible with the current system, reviewing user manuals, and starting off on what seems like a good note. If you can quickly find a suitable tool, congratulations, you’re lucky.

I apologize; it’s not that the resources don’t exist, but rather that the framework itself is too complex and consumes excessive resources. What beginners need is something small and streamlined. Consulting with colleagues on the testing team suggested building a custom framework—essentially, encapsulating existing unit testing frameworks into an automated testing framework.

Refer to the design concept of this project: https://github.com/wintests/pytestDemo

Why do we need frameworks?

The service has multiple deployment environments – development, testing, and pre-production – with the framework’s role being to provide a layer of abstraction, separating test cases and data. It supports environment-specific configurations for case data while also allowing shared data.

The underlying logic is to improve automation utilization. For more complex scenarios where data varies across different environments and has no inherent relationship, simply add a INLINE_CODE_0 tag when configuring the case data to specify the supported environment.

References

Please provide the Chinese text you want me to translate. I am ready when you are! Just paste the text here.