Jama Connect® Features in Five: Automated Testing
|
Jama Connect® Features in Five: Automated Testing
Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect®… in about five minutes.
In this Features in Five Integration Series video, Steven Pink – Senior Solutions Architect at Jama Software® – demonstrates an integration of automated test results with Jama Connect® through a Python Script and our open REST API.
VIDEO TRANSCRIPT
Steven Pink: Hello and welcome to the Features in Five Integration series. My name is Steven Pink, and I’m a Senior Solutions Architect here at Jama Software. Today we’ll be walking through a live demo of integrating some existing automated test results with Jama Connect through a Python script using our open REST API.
We make it possible for you to integrate Jama Connect with your preferred best-of-breed software to achieve Live Traceability™ across the end-to-end development cycle. Live Requirements Traceability is the ability for any engineer, at any time, to see the most up-to-date and complete upstream and downstream information or any requirement, no matter the stage of systems development or how many siloed tools and teams it spans.
This enables significant productivity and quality improvements and dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market.
RELATED: Requirements Traceability Benchmark
Pink: The goal of integrating automated test results is typically to better visualize test coverage for requirements. Jama Connect can identify and call out gaps in test coverage, as we see here, while also visualizing and reporting on the test results using filters, dashboards, and exportable reports.
Automated testing can be performed in a variety of ways, including the usage of automation servers and different frameworks. But regardless of the approach, all we need to integrate is to add requirement identifiers to our automated test results, so that they can be traced back to the requirements they cover and then make a call to the Jama Connect REST API to submit the latest results and traceability.
All right, now I want to talk about automated testing in Jama Connect. In this example project that we’re looking at, it’s a simple software development project where we’re gathering requirements, breaking those down into epics and stories, and then performing manual and automated tests.
In this example, our manual tests are being performed in Jama’s testing environment, but we have automated tests, that are actually automated test scripts, that we’re populating results into Jama with traceability, as a part of the automated test script, so that we have end-to-end traceability through our automated test results.
If I look at my manual test cases in the project hierarchy, we can see these manual tests have been created, some of them have been run, and results have been recorded. But if I switch over and look at my automated test cases, we’ll see there aren’t any yet. That’s because I haven’t run any automated test scripts.
RELATED: The Benefits of Jama Connect®: Supercharge Your Systems Development and Engineering Process
Pink: Now what I’m going to do is I’m going to execute an automated test script that will record some results for a few different tests. I’m going to run this module, and it’s going to start executing. And if we give it just another minute now.
If I go to my automated test cases, I’ll refresh this and you’ll see it’ll populate. We now have four automated test results that have been populated into Jama. We can populate these items with any kind of information from those automated test results, whether that be issues that arose during the execution or execution data. We can also keep track of whether they passed or failed, if we have a specific pass or fail parameter we can track through them.
The benefit of integrating automated testing with Jama Connect is that we can keep track of our traceability proactively as we run our automated tests. If I look at any one of these automated tests, you’ll see under the relationships, because in our test script we associated the test with a user story, that traceability has been built into this proactively. So when we execute our automated test, the results populate into Jama Connect with traceability.
Thank you for watching this Features in Five session on integrating automated test results to show requirement test coverage in Jama Connect. If you are an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you’re not yet a client, please visit our website at jamasoftware.com to learn more about the platform and how we can help optimize your development process. Thanks for watching.
To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series
Senior Solutions Architect at Jama Software
I'm a creative thinker with a passion for technology. I use my skills in requirements gathering, process improvement, prototyping, and project management to innovate and leverage technology to achieve measurable ROI. I pride myself on professionalism, flexibility, and meeting deadlines while working in an Agile environment.
Latest posts by Steven Pink (see all)