The importance of Software Testing

[Beth]

Some thoughts on how to use available technology to improve software
development and QA testing:

With the new platforms coming into play, developers are being
pressured to quickly release new, interesting and effective programs.
This means that development managers need to know what their teams are
working on, what bugs exist and in what stages, and what (if any)
feedback is coming in from clients. We’ve moved way beyond the days
when a basic spreadsheet (or email!) was sufficient for tracking the
development lifecycle.

In real time systems such as banks, hospitals, and airplanes,
releasing software that still contains bugs can cause real damage to a
company’s reputation, not to mention the people that rely on these
systems. Performing test cases on each function of the application
lets you ensure that the program performs as designed, and each
function produces the desired results, prior to release.

A testing manager needs a to communicate with everyone involved in the
testing process. Ideally, a test case should be analyzed by the tester
as well as the testing manager. When analyzing the tests, details on
past test results, previous testers, and processes used to generate
past test results are integral in comparing functionality of the
feature in its past and present iterations. If a bug is found, a
separate method is needed for tracking and fixing the issue. Keeping
track of these bugs and their current statuses is necessary for
completing the testing process. In an ideal world, any tools used for
bug tracking and test case tracking would be integrated, allowing easy
transfer of information from one data set to the other.

Additionally, testers need to be able to see what their peers are
doing in order to make critical decisions regarding their own tasks.
If the developers and testers are able to easily communicate and view
results from other team members, they can incorporate feedback and bug
fixes quickly and efficiently. Testing managers want to do everything
they can, and use every tool at their disposal, in order to facilitate
communication between and amongst teams.

In a detailed and organized test case scenario, it’s useful to have
the Test Case ID and Description, Expected Output, Actual Output,
Results, Remarks, Steps, Related Requirements, Test Category, Author,
and Time Spent on hand. Listing the detail of input, expected output,
preconditions and post conditions is a time consuming process. Testing
managers can increase efficiency, and decrease frustration, by having
a method or system in place to preserve this information for future
and related tests.

Of many different test case management solutions available, Software-
as-a-Service tools just make the most sense. SaaS providers not only
host the management software, but are responsible for maintaining,
updating and securing it. The low monthly fee is easily justified by
the reduction in IT overhead. Shifting maintenance and often time
consuming upgrades to the Elementool allows the development team to
focus on their product and business growth.

Companies which often have multiple projects in various phases at
various times, with developers and managers spread throughout the
globe, tend to find that the most effective solution is one which will
offer a detailed and organized test case scenario, easy archiving and
reporting and fluid communication between groups.

http://www.elementool.com/contact/articles/importanceoftesting.html

Anything to add?

Best,
Beth, from Elementool