The Micro Focus Service Virtualization team is proud to announce the release of version 5.0, introducing many new enhancements addressing a growing need on flexible deployment and usage of simulations in DevOps and Continuous Testing practices.
Mobile teams love working with AppPulse mobile to gain insights into the usage of their Android and iOS apps. However, collaboration quickly becomes a challenge if one needs to share the rich data from issues captured in the reports manually across teams. This is where AppPulse Mobile’s integration with the defect management systems Octane and Jira makes workflow seamless. In this blog we explore AppPulse Mobile’s ease of integration with Jira. But before we get started, let’s lay down the building blocks for this process.
1) Introduction: Here is a brief information about both the products:
a) AppPulse Mobile:Micro Focus AppPulse Mobile is an Android and IOS mobile app performance monitoring tool that tracks the real user experience of your mobile apps. Mobile teams receive actionable data to prioritize issues that are impacting most users to achieve a 5-star app rating.
b) Jira: Jira is a commercial software product which is developed by Atlassian. Jira is used to track bugs and can manage the projects.
2) Benefits: This integration helps stich together defect detection and defect management. Once integrated, users would be able to submit defects in Jira directly from the AppPulse Mobile reports for the following types of issues:
a) Mobile Application Crashes
b) Mobile Application Errors or Application slow performances
3) Key notes: One would need to consider the following points when integrating AppPulse mobile with Jira.
i. Keep the following details handy.
a) JIRA Account URL
b) User Name
ii. Enter the required fields and click Connect to JIRA to complete the integration process.
iii) Once connected to Jira, the Projects dropdown displays the available projects within the account. Select the desired project and click Save.
4) Submitting defects: Once the integration is successful, users can submit defects from the AppPulse Mobile reports. Refer to the Submit a defect section in the AppPulse mobile help page. The following screenshots could be used as reference.
5) Viewing defects in Jira: Login to the Jira and open the project that was selected in AppPulse Mobile. The submitted CR would be shown as below.
Note: Although the AppPulse Mobile Demo Application "Advantage Mobile Banking" allows the submission of defects, no real defect is submitted. Actual Jira defects can only be submitted from apps you create in AppPulse Mobile.
Haven’t tried AppPulse yet? Start your 30-day free trial here
The latest releases of Diagnostics and Real User Monitoring (RUM) are available now. These releases continue to strengthen both products’ rich feature set and technology support. Keep reading to learn more about these releases.
If you are reading this blog then most likely you are either exploring new ways of automating the SiteScope REST APIs or you are looking at enhancing the existing automation. If you are charged with building and supporting APIs in your group, you will be required to monitor these APIs at all times to ensure that there is continuous testing of these APIs during and after development. Additionally, the consumers of your APIs are most likely going to attempt to use it in different ways. Therefore, it is all the more important for you to include these as test cases and automate the API monitoring.
SiteScope REST APIs can be easily automated using the latest open source tool Karate developed by Intuit. It overcomes the short comings of the existing automation tools like Cucumber or Rest Assured and takes away the overhead of writing huge lines of code before you can start testing it.
This blog explains how to use Karate for automating any REST API call exposed by SiteScope.
2 . Use the basic-auth.js to configure the authentication for REST API. Following is an example of code snippet that I used.
3.Set up the configuration properties as required. karate-config.js file is the default configuration file that can be used for configuring the properties. Take a look at the code snippet that I used.
4.Write the feature file that includes all your test cases and scenarios. See the SiteScope API Reference Guide for parameters required by the SiteScope API calls.
SiteScope APIs test cases – Some examples
No prior knowledge required!
I started off with hardly any prior knowledge of Karate. And as you see, I was able to set up and start testing the SiteScope APIs. I was able to test a wide variety of complex validations using simple syntax as in the PUT and POST calls as shown in the preceding screen captures. SiteScope offers an exhaustive set of public APIs and having a tool that eases testing the APIs is a boon indeed for all the automation enthusiasts. Don’t you agree?
With the 9.40 release of Micro Focus Application Performance Management (APM), you can view the list of Business Process Monitoring agents and set the default settings in Application Health. Keep reading to find out how to utilize this capability.