For the first time, “ensure user satisfaction” is at the top of the list of QA and testing strategy goals, according to the tenth anniversary edition of the World Quality Report 2018-19 (WQR). This would have been unthinkable ten years ago. But with customer-centered innovation driving digital transformations, the adoption of agile and DevOps cultures, and a move to the Cloud, it is also resetting the expectations for testing.
Continue reading to learn about the key trends and recommendations in this year's report.
People hate when apps crash, slow down, freeze or otherwise behave badly. If your customer can’t reach or use your App, chances of success are slim! Mobile Center in the hands of trained users can help you build a memorable user experience.
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?