Software Test Tools Listing

A Guide to Software Test Tools

James Lyndsay - April 27, 2005

Testing a system well is harder than building it. In the face of new risks introduced by the ever-increasing complexity of software and hardware, test tools may be your only practical way to be confident that you've got just what you paid for. From gathering the initial requirements to supporting the system after it has been deployed, test tools are available to support all phases of a project. This article looks at the ways that test tools can be used to design, code, and (of course) test a system.

CRM Testing Throughout Implementation

James Lyndsay - October 13, 2004

In terms of strategic partnerships, the acquirer is responsible for judging how well customer relationship management (CRM) software will function on the equipment and at the site, and with staff, customers, and third-party applications. Acceptance testing involves three basic flavors: user acceptance, operational acceptance, and contractual acceptance. While it is not the only step involved when implementing a CRM system, testing is a fundamental way of finding information and will help you judge a system’s returns and pitfalls.

Program Testing Methodology
Part Two: Running Tests and Getting Approval

Dr. Edward J. Moskal - August 7, 2004

After testing procedures have been created and the type of test data has been determined, link or string testing, and system testing must be executed to ensure the job stream is correct and to locate errors before production. Backup and restart testing must be also be conducted to ensure that the restart points within the system are accurately defined. Finally, to demonstrate the benefits and functionality of the system, management and user approval should be received.

Program Testing Methodology
Part One: Preparing for Testing

Dr. Edward J. Moskal - August 6, 2004

Program testing and debugging is one of the most critical aspects of implementing a computer system. Without programs which properly work, the system will never process information and produce the output for which it was designed. Testing procedures should be established and testing roles should be demarcated between the programmer and the analyst. Once this is done, test data that can test the limits of the program should then be created.

Audit Considerations for Enterprise Software Implementations
Part 2: Applying Controls and Audit Emphasis

Joseph J. Strub - October 21, 2003

Whether audit expertise is provided by an internal staff or an independent, outside agency, calling in an audit specialist is as normal as calling in a kicking specialist in a penalty or field goal situation in football. Particularly when you consider the majority of an enterprise software implementation is all about testing, the present of an auditor as a functioning member of the project team makes perfect and logical sense.