Results 221 to 230 of about 22,449 (264)
Some of the next articles are maybe not open access.
Combinatorial testing of RESTful APIs
Proceedings of the 44th International Conference on Software Engineering, 2022Huayao Wu +3 more
openaire +2 more sources
2020
This chapter throws light on building representational state transfer (REST)-based services. Since we’ll be learning RESTful Web Services through our chosen language, Node.js, and using an awesome framework like Hapi, it’s first necessary to introduce ourselves to REST APIs and then understand how Hapi makes the process easy.
openaire +1 more source
This chapter throws light on building representational state transfer (REST)-based services. Since we’ll be learning RESTful Web Services through our chosen language, Node.js, and using an awesome framework like Hapi, it’s first necessary to introduce ourselves to REST APIs and then understand how Hapi makes the process easy.
openaire +1 more source
2015
It is extremely important to understand a REST-based architecture, meaning how the system will look if you’re basing all of your services in the REST style. But it is equally important to know what the internal architecture of those REST services will look like before you start working.
openaire +1 more source
It is extremely important to understand a REST-based architecture, meaning how the system will look if you’re basing all of your services in the REST style. But it is equally important to know what the internal architecture of those REST services will look like before you start working.
openaire +1 more source
2016
For a REST API we can produce an executable version of the documentation and allow users to interact with a system through its own documentation. In this sense, the documentation wouldn’t be a passive dust collector artifact (if stored in a printed form), but a handy UI to communicate with software.
openaire +1 more source
For a REST API we can produce an executable version of the documentation and allow users to interact with a system through its own documentation. In this sense, the documentation wouldn’t be a passive dust collector artifact (if stored in a printed form), but a handy UI to communicate with software.
openaire +1 more source
2014
Nowadays most of the big social network companies like Facebook and Twitter expose some services through REST API calls, making them easy to integrate with other applications. In this chapter, you are going to extend your code by adding some new functionality.
openaire +1 more source
Nowadays most of the big social network companies like Facebook and Twitter expose some services through REST API calls, making them easy to integrate with other applications. In this chapter, you are going to extend your code by adding some new functionality.
openaire +1 more source
2017
In this chapter, you’ll start storing in and fetching the data from the Node.js server instead of the hard-coded array of issues in the browser’s memory. The objective is to get used to interacting with the server via REST APIs.
openaire +1 more source
In this chapter, you’ll start storing in and fetching the data from the Node.js server instead of the hard-coded array of issues in the browser’s memory. The objective is to get used to interacting with the server via REST APIs.
openaire +1 more source
2016
The tests should follow the use cases (both main and exceptional routes) by always starting from the home page, and reacting to content presented by the server.
openaire +1 more source
The tests should follow the use cases (both main and exceptional routes) by always starting from the home page, and reacting to content presented by the server.
openaire +1 more source