During a recent consulting assignment, a tester told me he spent 90 percent of his time setting up test conditions. The application allowed colleges and other large organizations to configure their workflow for payment processing. One school might set up self-service kiosks, while another might have a cash window where the teller could only authorize up to a certain dollar amount. Still others might require a manager to cancel or approve a transaction over a certain dollar amount. Some schools took certain credit cards, while others accepted cash only. To reproduce any of these conditions, the tester had to log in, create a workflow manually, and establish a set of users with the right permissions before finally doing the testing. When we talked about automation approaches, our initial conversation was about tools to drive the user interface. For example, a batch script like this:
Some software testing tasks, such as extensive low-level interface regression testing, can be laborious and time-consuming to do manually. In addition, a manual approach might not always be effective in finding certain classes of defects. Test automation offers a possibility to perform these types of testing effectively. Once automated tests have been developed, they can be run quickly and repeatedly. Many times, this can be a cost-effective method for regression testing of software products that have a long maintenance life. Even minor patches over the lifetime of the application can cause existing features to break which were working at an earlier point in time.
The software automatically syncs business profiles to a single dashboards, where multiple users can view reports and corporate accounts. It is capable of generating profit and loss and trade sheets, invoices and billing, all which are accessible via mobile devices. Custom reports and feeds can likewise be created from the dashboard. Popular integrations include Quickbooks Online Payroll and Intuit GoPayment.
Cucumber is a tool for working with the executable specifications. The executable specifications are used for greater collaboration among IT and business teams. This tool is useful for writing acceptance tests for the web application. Cucumber offers feature files that can be used as a go-to-documents by Business Analysts, Developers, and Testers, etc. Initially, Cucumber was implemented in Ruby language but later it was extended to the Java framework. Cucumber supports languages such as Perl, PHP, Python, Net etc.
Available in both open source and commercial versions, Sahi is centered around web-based application testing. Sahi is used inside of a browser, and can record testing processes that are done against web-based applications. The browser creates an easy-to-use environment in which elements of the application can be selected and tested, and tests can be recorded and repeated for automation. Playback functionality further makes it easy to pare down to errors.
No one has jumped into the desktop accounting software arena for over two decades. The survivors of what was once a crowded field have been around since the early 90s. They are QuickBooks (the desktop version), Sage 50c (which started its life as Peachtree Accounting), and AccountEdge Pro (formerly MYOB), the latter two of which are included in the table above.
This article uses the term “tester” to refer to the person involved in testing software with automation tools. It is not meant to distinguish by job title or technical proficiency. Jim Hazen describes himself as a hybrid, or “technical tester,” because he can write test scripts and develop what he refers to as “testware.” The trend is to hire for multiple skillsets, but that does not mean the non-technical stakeholders involved in software development don’t benefit from automation testing.