https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232060#M10073 <P>I would ideally like to catch the chances of developers breaking splunk dashboards/ reports at an early stage in the development life cycle (may at unit testing/integration testing stage) . Is there a way Splunk exposes what fields it used in a report or dashboard through some api so that I can write some unit tests to make sure we are still sending the fields etc.?</P> Wed, 18 Jan 2017 10:23:58 GMT rajivchadha 2017-01-18T10:23:58Z https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232060#M10073 <P>I would ideally like to catch the chances of developers breaking splunk dashboards/ reports at an early stage in the development life cycle (may at unit testing/integration testing stage) . Is there a way Splunk exposes what fields it used in a report or dashboard through some api so that I can write some unit tests to make sure we are still sending the fields etc.?</P> Wed, 18 Jan 2017 10:23:58 GMT https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232060#M10073 rajivchadha 2017-01-18T10:23:58Z https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232061#M10074 <P>As far as I know, there is not a readily available or unified testing API for dashboards or apps in Splunk. You would likely have to take a similar approach taken in Splunk's own example shown here (<A href="http://dev.splunk.com/view/SP-CAAAE2V#Platformandtools:akitbagforourjourney-Automatingadvancedcontrols">http://dev.splunk.com/view/SP-CAAAE2V#Platformandtools:akitbagforourjourney-Automatingadvancedcontrols</A>) and write some test automation tools using one of the SDKs (Java, Python, or C#). You would also need a tool like Eventgen (<A href="https://splunkbase.splunk.com/app/1924/">https://splunkbase.splunk.com/app/1924/</A>) to create sample data on a regular basis.</P> <P>If all you care about is specific functionality of certain reports or searches, you could try coming up with a simpler mechanism using the REST API and a known sample data set to see if the returned results are changing. This would only be testing the searches and data, not dashboards and interactivity.</P> Wed, 18 Jan 2017 12:31:30 GMT https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232061#M10074 rjthibod 2017-01-18T12:31:30Z https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232062#M10075 <P>thanks, will take a look</P> Wed, 18 Jan 2017 17:12:09 GMT https://community.splunk.com/t5/Reporting/Minimize-the-chances-of-developers-breaking-Splunk-reports/m-p/232062#M10075 rajivchadha 2017-01-18T17:12:09Z