Hi friends!!! Today, I would like to introduce vREST NG CLI which is the command line partner of vREST NG Application. With vREST NG CLI, you will be able to execute your API tests on the command line as well. It uses the same runner component as used by the vREST NG Application itself. So, whatever works in the vREST NG UI Application will seamlessly work on the command line as well using vREST NG CLI without any further hassle. It provides beautiful and usable reports to debug your API failures quickly.Continue reading Introducing vREST NG CLI – A command line partner of vREST NG Application
Today, in this post, I will highlight the process of most effective API automation Testing process and benefits of that process. This process makes use of swagger files and excel sheets and combines the power of these powerful tools to make your API testing experience more seamless. I have personally applied this process in various projects and found it to be very effective.
This process can be adopted with any API test automation tool or framework which supports swagger import process and reading test data from excel sheets. For a specific guide about detailed instructions, you may look at my article on Swagger + Excel Sheets, a wonderful way of validating REST APIs.Continue reading Boost your API Test efficiency using swagger and excel sheets
Hi guys, today I will discuss about how easy it is to perform API Testing using vREST NG irrespective of whether you are a developer, non developer or tester. vREST NG provides simple interface so that any body can write API test cases quickly without writing a single line of code.Continue reading vREST NG – Taking your API Testing experience to the next level
Swagger Files (aka OpenAPI Specification) is the most popular way for documenting API specifications and Excel sheet provides an easy and simple way of writing structured data. Anybody can write data in excel sheet irrespective of their programming skills. Introducing vREST NG (An enterprise ready application for Automated API Testing), which combines the power of both to make your API Testing experience more seamless. The approach is also known as Data Driven Testing.
Continue reading Swagger + Excel Sheets, a wonderful way of validating REST APIs
Data Driven testing is an approach in which test data is written separately from the test logic or script.
Swagger (now known as OpenAPI) is a well-known framework for describing the API specifications. Swagger removes ambiguity among multiple teams (e.g. frontend team, backend team, testing team) by having the proper API specification. And development and testing teams can work in parallel by referring the same spec.
Today in this post, we will look at how the swagger spec also helps us in making the automated API validation process easier. We have developed a tool named as vREST NG for validating the REST APIs and it also imports the swagger specification and makes the validation process against the imported schema much easier. Continue reading Easily validate your REST APIs by using the swagger definitions
Adoption of REST APIs has increased manifold in recent days and REST has become a leading standard for building web APIs. The era of pure desktop-based applications is continuously going down. People are shifting from NG to web and further mobile-based applications.
Most of the web-based applications or mobile applications are backed by REST APIs. Testing this type of applications has become a major challenge. Various tools/frameworks/libraries (utilities) are there to automate the testing activity. People choose these utilities depending upon their context, environment, budget and skill level, etc.
In this post, we will discuss the need for automation followed by various challenges behind REST API Automation Testing. I will appreciate questions/feedback if you have any ☺
Version control of test data also plays a great role in the same manner as you can’t live without source code version control. You should definitely think of this dimension while choosing the test automation tool. Otherwise, you will face various issues once you have adopted the tool in the later run. The following issues are centered around version control:
- Test data Auditing (Who changed what data at what time)
- Review process
- Minimizing merge conflicts
- Team collaboration or sharing issues
- Backup and restore test data
In the API Testing world, if an automated testing tool doesn’t provide reusability then you will pay a great cost while maintaining the test suites over a period of time. Reusability and maintainability are two sides of the same coin. If reusability decreases then maintainability also decreases and vice versa. If you are having a small number of APIs/test cases then reusability might not be a concern for you, but if your whole architecture is based around APIs then reusability plays a great role while creating the automated test suites for those APIs. And it is very important to think about this dimension while choosing the API automation framework/tool. We should follow the DRY (Do not repeat yourself) principle.