What is Test management tools?

The features of test management tools are given below. Some tools will provide all of these features; others may provide one or more of the features. [Read more…]

What is Configuration management tools?

Configuration management tools are not strictly testing tools either, but good configuration management is critical for controlled testing.

To understand this better let us take an example, a test group started testing the software, expecting to find the usual quite high number of problems. But to their surprise, the software seemed to be much better than usual this time – very few defects were found.  [Read more…]

What is Incident management tools?

Incident management tool is also known as a defect-tracking tool, a defect-management tool, a bug-tracking tool or a bug-management tool. However, ‘incident management tool’ is perhaps a better name for it because not all of the things tracked are actually defects or bugs; incidents may also be perceived problems, anomalies that are not necessarily be defects. Also what is normally recorded is information about the failure (not the defect) that was generated at the time of testing and the information about the defect that caused that failure would come to light when someone (e.g. a developer) begins to look into the failure. [Read more…]

What is Requirements management tools?

Since the tests are based on requirements, the better the quality of the requirements, the easier it will be to write tests from them. It is equally important to be able to trace tests to requirements and requirements to tests. [Read more…]

What is configuration management in software testing?

Configuration management is a topic that often confuses new practitioners. So, let me describe it briefly:

  • Configuration management determines clearly about the items that make up the software or system. These items include source code, test scripts, third-party software, hardware, data and both development and test documentation.
  • Configuration management is also about making sure that these items are managed carefully, thoroughly and attentively during the entire project and product life cycle.
  • Configuration management has a number of important implications for testing. Like configuration management allows the testers to manage their testware and test results using the same configuration management mechanisms.
  • Configuration management also supports the build process, which is important for delivery of a test release into the test environment. Simply sending Zip archives by e-mail will not be sufficient, because there are too many opportunities for such archives to become polluted with undesirable contents or to harbor left-over previous versions of items. Especially in later phases of testing, it is critical to have a solid, reliable way of delivering test items that work and are the proper version.
  • Last but not least, configuration management allows us to keep the record of what is being tested to the underlying files and components that make it up. This is very important. Let us take an example, when we report defects, we need to report them against something, something which is version controlled. If it is not clear what we found the defect in, the programmers will have a very tough time of finding the defect in order to fix it. For the kind of test reports discussed earlier to have any meaning, we must be able to trace the test results back to what exactly we tested.

Ideally, when testers receive an organized, version-controlled test release from a change-managed source code repository, it is along with a test item trans-mittal report or release notes. [IEEE 829] provides a useful guideline for what goes into such a report. Release notes are not always so formal and do not always contain all the information shown.

Configuration managemement or Item transmittal report template

Configuration management is a topic that is very complex. So, advanced planning is very important to make this work. During the project planning stage – and perhaps as part of your own test plan – make sure that configuration management procedures and tools are selected. As the project proceeds, the configuration process and mechanisms must be implemented, and the key interfaces to the rest of the development process should be documented.