TBValdez's avatar
10 years ago
Accepted for Discussion

Test Metrics Reporting

Recommending that the reporting feature within QA Complete be updated with more flexibility and user friendliness.  One thing our QA team does for reporting is generate test metrics reports which list the Test Set Name or Test Name, the # of Tests (not runs), # passed, # failed, # blocked.  While we understand the logic behind displaying the values off the # of runs for the tests for reporting purposes, our customers and project teams do not want to know that we executed a test set 3 times and it failed twice.  They want to know the # of total tests (baseline #), # passed, # failed, # blocked and not based off of execution.  They do not want to see that we ran Test A, itertion #30, 6 times.


For example, if Test Set A has 5 tests but with tokenization has 300 test iterations the report needs to display 5 tests for this Test Set and note the # failed, # passed, # blocked.  Right now the canned reports in QA Complete are displaying this based on the tokenization iterations which is too detailed.  We have spent hours working with these reports but with reporting being built around Crystal Reports this limits our ability to build the report we need. 


  • gxwheels152's avatar
    Occasional Contributor

    Also need Trendline Reporting for tests and test runs over time

  • nemox's avatar
    Occasional Visitor

    Hello there, how I can download the Test Metrics Reporting? API supported download? Don't found this function in the Test Metrics page..

  • ublixalvet's avatar
    Occasional Visitor
    • Test Metrics Reporting provides valuable insights into the effectiveness and progress of software testing efforts.
    • It includes various metrics such as test coverage, defect density, test execution status, and defect resolution time.
    • Test Metrics Reporting enables stakeholders to assess the quality and reliability of the software under test.
    • It helps in identifying areas for improvement in the testing process and prioritizing test activities.
    • Test Metrics Reporting facilitates data-driven decision-making and risk management during the software development lifecycle.
    • Utilizing Test Metrics Reporting fosters transparency and accountability within the testing team and across project stakeholders.
    • It serves as a tool for benchmarking and comparing testing performance over time or across different projects.
    • Test Metrics Reporting empowers teams to track progress towards testing goals and objectives.
    • It supports continuous improvement efforts by providing actionable insights for optimizing testing strategies.
    • Test Metrics Reporting enhances communication and collaboration among team members by providing a common understanding of testing performance.
    • Leveraging resources like game can further augment test metrics reporting by offering additional insights, best practices, and tools for optimizing testing processes.
    • Ultimately, Test Metrics Reporting contributes to delivering high-quality software products that meet user expectations and requirements.
    • gxwheels152's avatar
      Occasional Contributor

      I'm confused by this comment -- there's not a link to the service page, but lots of information about the service