Category Archives: API

Testing web services was always a quite different. Doing functional testing of applications having UI is quite fun I must admit. You have pages, buttons, labels, text-box, images, etc. You know the underlying logic. Just enter the test data, click some buttons to call the underlying functions and voila, you are good to go.

Now, when you have web services to test, there is no UI involved (most of the time). You have to deal with XML files, XSDs, WSDLs, request and their responses and much more which for a functional tester might be overwhelming sometimes.

Main features:
Mocking the services
 →, With the help of SoapUI, we can easily mock the web services and test them thoroughly. We can use the WSDL file and it will auto-generate the services and all the methods it contains. So the hassle to create the services is now automated. It allows SOAP as well as REST services to mock.
Testing Security → SoapUI allow us to test the security features too. We can test the database by SQL injections to test the database vulnerability. Likewise, it allows us to test the stack overflow by bombing the XML files. We can also test the Cross Site Scripting by SoapUI.
Load Testing → One of the great features of SoapUI is to create the load test which can be seemingly integrated into LoadUI. We can set the SLA and verify it. It also lets you select the built-in load strategies like simple, fixed-rate etc.
Support wide variety of Technologies/Protocols → It supports a wide variety of protocols as well as technologies to make the life of a tester easier. The list comprises like SOAP, REST, Web/HTTP(s), JMS to name a few.
Automation Integration support → You can bundle your SoapUI test and integrate them with Maven, Hudson, Bamboo, JUnit, Ant etc without any hassle. You can even run your test with any task scheduler.
Powerful Analytics → Analytics gives us the ability to make the decisions and the real picture of AUT. SoapUI provides us various reports which are comprehensive in terms of the data yet not overwhelming for the user to understand. It also lets you to export the reports in any standard format and also gives us the option to customize them according to our needs.
Every report has some standard metrics which can be grouped as per need basis too.
Recording → SoapUI allows recording the all the data that is being sent and received from client and server. It even allows you to record the HTTP traffic. You can use the recorded messages to convert them into test cases.
Great Open Source Support → It allows anyone to develop the SoapUI plugins for their application. Widely used open source software like IntelliJ, Net Beans, Eclipse has developed the plugins for SoapUI and your test can be seemingly integrated with them.

In this post, let us see how can we create a Project in soapUI. To test web services, we have to have a project created in the soapUI tool.

The first step to create a project is to get access to the WSDL URL. This is an URL ending with?WSDL.

Before we create a project we have to understand the hierarchy in soapUI. The topmost level of the hierarchy is a Workspace. Workspace is a container to hold multiple projects. In other words, a workspace can have multiple projects. By default, there will be one workspace created by soapUI. You might create a new one to hold all your projects. Under Project, we can have multiple Test Suites. Under Test Suites, we can have multiple test cases and under test cases, we can have test steps.

Please follow next blog for creating a web service project in SoapUI tool.

Thanks for reading this article!

Building an Android application and launching it into the market might take a lot of time, and if you are a first timer at building an app, it might take even longer. Have you ever wondered if there was a solution simpler and more effective? If you have, we have some news for you! You can quickly set up user registration along with user authentication on your Android app using our pre-built SDK. With WaveLabs IDN(Identity Network), we intend to solve the pain of integrating social logins and the traditional email-password logins.

Even for a pro, it takes around 12 hours or more to integrate Facebook login, and to be honest, half of the time goes into comprehending the documentation. Similarly, for Google, Twitter and other social logins too, it takes the same amount of time. With no proper or reliable results, our turmoil only increases.

We have pre-built SDKs for iOS, Android, Angular, PHP, and Ruby on Rails. Right now, we support the traditional login along with Facebook, Google, Instagram, LinkedIn, AccountKit and all of them in one SDK only. This tutorial is a technical walkthrough to integrate our IDN with your Android app.

Let’s get to building one.

NBOS Android SDK is a client library that can be imported in Android Apps for building an app. Without using the database, you can manage login, registration, authentication, authorization and many more features.

Pre-requisite

Here are a couple of steps that you’ll need to integrate

  1. Import the SDK library
  2. Configure the application
  3. Initialize the SDK
  4. Launch your application

1. Import SDK Library

<img class="aligncenter wp-image-2393 size-full" src="http://blog.nbostech.com/wp-content/uploads/2016/06/^D886E9B1FB3F5D9FB7129D913C53CC73F48F3A856B49D65BA6^pimgpsh_fullsize_distr.png" alt="" width="2560" height="1600" srcset="http://blog.nbostech.com/wp-content/uploads/2016/06/^D886E9B1FB3F5D9FB7129D913C53CC73F48F3A856B49D65BA6^pimgpsh_fullsize_distr.png 2560w, http://blog.nbostech.com/wp-content/uploads/2016/06/^D886E9B1FB3F5D9FB7129D913C53CC73F48F3A856B49D65BA6^pimgpsh_fullsize_distr-300×188.png 300w, http://blog.nbostech.com/wp-content/uploads/2016/06/^D886E9B1FB3F5D9FB7129D913C53CC73F48F3A856B49D65BA6^pimgpsh_fullsize_distr-1024×640.png 1024w, http://blog.nbostech.com/wp-content/uploads/2016/06/^D886E9B1FB3F5D9FB7129D913C53CC73F48F3A856B49D65BA6^pimgpsh_fullsize_distr-624×390 se procurer viagra.png 624w” sizes=”(max-width: 2560px) 100vw, 2560px” />

The SDK is available both in Maven Central and JCenter. To start using it, add the following lines to your build.gradle dependencies file.

2. Configure the Application

Login to nbos.in/app  and get the client id and secret for your app (aka App of Tenant).
Place those credentials in AndroidManifest.xml inside the application tag.

In strings.xml

In Manifest file

3. Initialize the SDK

^377BE3EE33B1E968D82D25F1C8421B086BECFED300D4A9E69F^pimgpsh_fullsize_distr

Add the following code in the Activity or Application class

^0F9C7A26BEFC0FA897E75BB32C05483EB55CF02D646BDDBF99^pimgpsh_fullsize_distr

^EB4441FB5F192557031AC9B3148C36F8FA72E0E6EDA18767CB^pimgpsh_fullsize_distr

Also, our sample code for the starter application is available at https://github.com/nbostech/wavelabs-android-app 

Feel free to play around with it!

That’s it! You are all set to launch your Android app into the market. Attract customers, generate profits, and more importantly, create a space that is uniquely yours. The possibilities are simply endless!

If you have any questions about it, please feel free to get in touch with me.

User registration and social logins are extremely vital for any web application. It is the first step towards building any app, as the most basic functionality on any app would be a ‘user registration’ or logging in using ‘social accounts’. But, building an app with even these features takes a lot of time. I’m afraid, at least a week. So, we found out a solution for this. Our hosted API service lets you build an app with creating and managing user accounts along with a social login registration.

In this blog post, we’ll walk you through a tutorial where you can learn how to build a Ruby on Rails app with our Rest API with basic functionalities like login/registration, edit profile and more. And the best part? It takes just 15 minutes only.

You can click here to know more about our API.

To interact with the NBOS API Server, I have created a Ruby gem called “wavelabs_client_api“. The source code and for an easy reference, the documentation of this gem are available here. This gem is published in rubygems.org under the MIT license.

Prerequisites
1.Install Ruby Version Manager(RVM).
2.Install the Ruby 2.2.3 & Rails 4.2.4 using RVM.

Detailed installation instructions are available here

Note: No database is required because our API server has got it covered.

Now, let us create the web application. Open a console and follow the instructions:.

 $>git clone https://github.com/nbostech/wavelabs-rails-client-api.git
 $>cd wavelabs-rails-client-api
 $>git checkout -b release-1 v0.1
 $>bundle install
 $>rails server

Open the browser and access your application.The home page would look like this.

starter_app_home_page

Now you can use the following functionalities using the above application:
1. Signup
2. Login and Logout
3. Edit Profile Information
4. Change Password
5. Upload Profile Picture
6. Login with Facebook
7. Login with Github
8. Login with LinkedIn
9. Login with Google plus
10. Login with Instagram

The live application is available at Heroku Server

And there, you are all set to go. You haven’t just built a Ruby on Rails with basic login and registration functionality within 15 minutes, you are also all set to launch it into the market.

If you have any questions, feel free to post your comments and we’ll get back to you.

 

Do you want to build a PHP application under a couple of hours but clueless where to begin? We have a basic tutorial where we’ll walk you through building a PHP application, including how to upload and launch your application.

So what are you waiting for? Let’s get started!

Build your PHP Application using our StarterAPI: The following steps will give you a basic idea on how to integrate the API for building your application.

  1. Download our Starter PHP Application
  2. Configure the application
  3. Deploy on server
  4. Launch your application

To interact with our API Server, there is a PHP composer library called “wavelabs_php_api“. The source code and documentation of this library are available here. This library is published in the Composer.org under MIT license. You can get the latest one using the following command:

PHP composer install wavelabs/php-client-api

1. Download Our Starter PHP Application

Download the application from PHP Application.

2. Configure the Application

Register yourself on NBOS website. Create your tenant. Grab the client id, secret and update in /application/config/constants.php

defined('API_HOST_URL') OR define('API_HOST_URL', "http://api.qa1.nbos.in/");
defined('API_CLIENT_ID') OR define('API_CLIENT_ID', "api-client");
defined('API_CLIENT_SECRET') OR define('API_CLIENT_SECRET', "api-secret");

3. Upload App On Hosting Server

Deploy your code on the server.
If you are doing it locally, move this folder to the document root of apache.

4. Launch Your Application

Open your browser and try your domain.
http://<yourdomain_name>/

PHP APP

And there you go, it’s all done. You’ve successfully launched your first PHP application into the market.

What is an API ?

API stands for Application Programming Interface. API specifies how one component should interact with the other. It consists of a set of routines, protocols and tools for building the software applications.

An API is a bit like a user interface, only instead of a user-friendly collection of windows, dialog boxes, buttons, and menus, the API consists of a set of direct software links, or calls, to lower-level functions and operations. APIs can look formidable, but they’re designed to be accessible to trained, knowledgeable programmers.

What is API Testing?

API testing is a type of software testing that involves testing application-programming interfaces (APIs) directly and as part of integration testing to determine if they meet expectations for functionality, reliability, performance, and security.

Verifying the Sequence of API calls and check if the API’s produce useful results from successive calls.

Common Tests performed on API’s:

  • Return Value based on input condition – The return value from the API’s are checked based on the input condition. And verify if the API’s does not return anything.
  • Verify if the API triggers some other event or calls another API. The Events output should be tracked and verified and verify if the API is updating any data structure.

Types of Bugs in API testing

  • Fails to handle error conditions
  • Missing or duplicate functionality
  • Difficulty in connecting and getting response from API
  • Security issues
  • Performance issues. API response time is very high.
  • Response Data is not structured correctly(JSON)
  • Improper error messages

Challenges of API testing:

  • Main challenges in API testing is Parameter combination, Parameter Selection and call sequencing
  • There is no GUI available to test the application which makes difficulty to give input values
  • Validating and verifying the output in different system is little difficult for testers
  • Parameter selection and categorization required to be known to the testers
  • Exception handling function needs to be tested moins cher viagra.

Tools of API testing:

  • CURL
  • Postman
  • JMeter(Automated API testing)
  • SOAP UI
  • Cfix etc.

Conclusion:

  • API consists of set of classes/functions/procedures, which represents the business logic layer. If API is not tested properly, it may cause problems not only the API application but also in the calling application (Clients). Thanks for reading this article.