Versions Compared

Old Version 3

changes.mady.by.user Sofia Canario

Saved on

compared with

New Version 4

changes.mady.by.user Sofia Canario

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UI Steps
UI Step

How to use a Gadget?


A gadget allows you to display dynamic content inside a dashboard, these gadgets can be as simple as lists based on filters, or complex reports. 

You can add gadgets to your personal dashboard, and even share dashboards with other users. By doing this, you are personalizing your own view of information and build a way to get insights that will help you to make better decisions. 


To use a gadget:

  1. Go to the dashboard by selecting the Dashboards link in the header.
  2. If you don't already have a dashboard, select Manage Dashboards from the dropdown, then Create new dashboard.
  3. Once your dashboard is created, on the dashboard, select Add Gadget.
  4. Use the gadget wizard to choose the gadgets you want to add.



Tip

After loading all the gadgets available, you can search for "xray" to easily find the gadgets made available by Xray.



UI Step

Gadgets available by Xray


GadgetExampleWhat to use for?Similar to 
Overall Requirements Coverage Gadget

Quick way of evaluating the current coverage status for a set of requirements, that can span one or more projects. Overall Requirements Coverage Report
Historical Daily Requirements Coverage Gadget

Provide visibility into the evolution of the coverage status of your project's requirements for last N days, for a given version of the system.

Evaluate your progress, i.e., if you're closer to having all your requirements properly tested and ready for deployment.

Historical Requirement Coverage Report
Test Runs Summary

Check status of a group of scheduled/executed test runs (e.g., from a Test Plan) in order to evaluate the testing effort.

 

Some possible usage scenarios:

  • analyze the Test Runs from a Test Execution
  • analyze the Test Runs from all Test Executions belonging to a Test Plan
  • depict the testing results for a given component, in the context of a Test Execution or Test Plan
  • see how the testing is progressing in terms of scheduled runs, from the Test Run assignee perspective
  • see how the testing is progressing in terms of scheduled runs, based on the Test priority
  • see how failures, or some other test run statuses, are impacting components
    • analyze the Test Runs of a given Test Environment

    		N/A