Friday, 9 October 2015

Testing Tools

Using Automation tools we can record actions that taken against an application. The Main agenda is to record enhance and execute the application in order to find out defects. Test scripts are derived from these recordings which are then used for subsequent test execution. We have certain benefits and risks in using these tools for automation.
Benefits in Using tools is :
  • Repetitive works is reduced like regression tests and re-entering the same code for same test data.
  • Tools are designed with greater consistency and repeatability
  • Objective assessment like static measures and coverages of code are made easy
  • Ease of access the information about tests or testing ( example: statistics and graphs about test progress)

Risks in Using Tools:
  • Unrealistic expectations for the tools
  • Underestimating the time, cost and effort which is needed to get a tool introduced initially in an organization
  • Underestimating the time and effort needed to achieve significant and continuing benefits from the tool
  • Over- reliance on the tool.

The tools in software testing are categorized into 5 types which purely depends on the nature of test they undergo . They are
  • Test Management Tools
  • Static Testing Tools
  • Test Execution Tools
  • Test Specification tools
  • Test Monitoring and Performance tools

Test management tools : These tools are used to store information on how testing is to be done, plan testing activities and report the status of quality assurance activities. The tools have different approaches in testing and thus have different sets of features. Generally they are used to maintain and plan manual testing, run or gather execution data from automated tests, manage multiple environments and to enter information about found defects. Test management tools offer the purpose of streamlining the testing process and allow quick access to analyze the data, collaborative tools and easy communication across multiple project teams. Many test management tools are purely based on Requirements management capabilities to streamline test case design from the requirements. Tracking of defects and project tasks are done within one application to further simplify the testing.

Static analysis tools: These tools are generally used by developers as part of the development and component testing process. The key aspect is that the code (or other artifact) is not executed or run but the tool itself is executed, and the source code we are interested in is the input data to the tool. Static analysis tools are an extension of compiler technology, in fact some compilers do offer static analysis features.

Testing Specification: It is a detailed summary of what scenarios will be tested, how they will be tested, how often they will be tested, and so on and so forth, for a given feature. Trying to include all Editor Features or all Window Management Features into one Test Specification would make it too large to effectively read. However, a Test Plan is a collection of all test specifications for a given area. The Test Plan contains a high-level overview of what is tested for the given feature area.

Test Performance and Monitoring tools: Monitoring tools are used to continuously keep track of the status of the system in use, in order to have the earliest warning of failures, defects or problems and to improve them. There are monitoring tools for servers, networks, databases, security, performance, website and internet usage, and applications. These tools are used to check the performance of tool under stress , load, and other features.

Test Execution Tools: When people talk about the ‘testing tool’, it is mostly a test execution tool that they think of, basically a tool that can run tests. This type of tool is also known as a ‘test running tool’. Most tools of this type get started by capturing or recording manual tests; hence they are also known as ‘capture/playback’ tools, ‘capture/replay’ tools or ‘record/playback’ tools. It is similar as recording a television program, and playing it back.. These tools are mostly used to check the functionality of the application or software




2 comments:

  1. Thanks for providing complete information about static testing tools, tools benefits and risk related to this tool. I found static testing tools is very useful.

    ReplyDelete
    Replies
    1. Pleasure is Mine n Thanq for reading my blog

      Delete