Rommana Bug Tracking process creates the standalone issue reports, offers optional linking of an issue report to a necessity, a use case, a situation. It also offers the capability to maintain dependence between issue reports and test cases. These tools provide up-to-date thorough status of issue reports and advancement on handling them. Bug Tracking Tools allow tracking in predictable and actual hours for working with issues; Rommana offers a seamless incorporation of Jira as a bug tracking tool with Rommana and provides traceability of Jira bug reports back to test cases, situations, use cases and requirements in the Rommana source, and many others.
Some of the capabilities of Bug Tracking Tools in Rommana are as follows:
• Creates standalone issue reports not linked to any test cases, scenarios, use cases, or requirements.
• Manages issue reports all along their life cycle as they are managed by the development team and the test team.
• Can link an issue report to a requirement, a scenario, a use case or attest case.
• Maintains the dependency between issue reports and test cases
• Provides updated detailed status of issue reports and progress while handling them
When working with agile projects, the Bug Tracking Tools can burn down chart for issue reports and provide detailed information in relation to creating and fixing (burning) issue reports over the progression of a sprint or a release. It also allows the developers to provide impression analysis information for each fix for the test crew to use for operative regression testing. These tools allow tracking estimated and actual hours for working with issues. By providing the dependency between bug reports in Jira and test cases in Rommana, it becomes a sought after tools in the market. Moreover, Bug Tracking Tools also have the ability to move issue reports between releases and sprints (iterations)
For more information please visit us at http://www.rommanasoftware.com/