This article will help software testers to gain an understanding of the specific practices that are commonly practiced by financial service providers in financial software testing of banking and financial services applications. Banking applications include core banking, retail, private, corporate, investment, credit card applications and financial services applications like payment gateways, mutual funds applications.
This 50 pages report from the Software Engineering Institute on unit testing and analysis examines the techniques, assessment and management of unit analysis and testing.
Wild test suites often contain inefficient or ineffective tests. Working with a code base full of these beasts is frustrating and time consuming. This safari will help you identify and hunt down common testing anti-patterns. Afterwards you’ll know how to approach a test suite full of beasts without losing your mind or your life.
Mobile applications (or apps) are the current trend in the evolution of software development where mobile devices become the client device rather than a PC. Load testing of mobile apps requires some specific practices. The Methods & Tools magazine a published in its last issues a series of articles about this topic. The articles were targeting each a specific component of the mobile software ecosystem: the device, the server and the network.
Behavior-driven development (BDD) is an increasingly popular variation on test-driven development, which helps developers think more in terms of “executable specifications” than in terms of conventional tests. There are dozens of BDD tools for the JVM out there—how do you know what to use and when?
In my previous articles, PHP Unit Testing with PHPUnit and Using Mocks and Stubs in PHPUnit, I have showed how to set up PHPUnit and how to get started with unit tests and how to handle mocking and stubbing objects in order to effectively isolate your code under test. This article will explore a few ways to get the most out of your PHPUnit tests.
In the context of Java EE 6, unit tests are nice but worthless. Unit and integration tests execute chunks of the business logic in a single thread. Back-end resources and shared states are simulated with mocks.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates