Results 171 to 180 of about 507 (213)
Some of the next articles are maybe not open access.
2016
In an ideal world, we wouldn’t need explicit version numbers (or any version identifiers for that matter) in our REST APIs. If you think that such a world doesn’t exist, well, it is all around us. It is the Web! Our web browsers can handle all sorts of web sites, usually without significant problems (we assume that our modern browser understands ...
openaire +1 more source
In an ideal world, we wouldn’t need explicit version numbers (or any version identifiers for that matter) in our REST APIs. If you think that such a world doesn’t exist, well, it is all around us. It is the Web! Our web browsers can handle all sorts of web sites, usually without significant problems (we assume that our modern browser understands ...
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
2017
APIs are not new. They’ve served as interfaces that enable applications to communicate with each other for decades. But the role of APIs has changed dramatically in the last few years. Innovative companies have discovered that APIs can be used as an interface to the business, allowing them to monetize digital assets, extend their value proposition with
openaire +1 more source
APIs are not new. They’ve served as interfaces that enable applications to communicate with each other for decades. But the role of APIs has changed dramatically in the last few years. Innovative companies have discovered that APIs can be used as an interface to the business, allowing them to monetize digital assets, extend their value proposition with
openaire +1 more source
2015
In the previous chapter, we saw how to perform a great range of tasks using the JavaScript Object Model (JSOM) and the Etherson method. In this chapter, we’ll look at the same tasks, except how to perform them using the REST API. To that end, a lot of the HTML from the previous chapter will be similar and the results will be the same.
openaire +1 more source
In the previous chapter, we saw how to perform a great range of tasks using the JavaScript Object Model (JSOM) and the Etherson method. In this chapter, we’ll look at the same tasks, except how to perform them using the REST API. To that end, a lot of the HTML from the previous chapter will be similar and the results will be the same.
openaire +1 more source
HeadREST: A Specification Language for RESTful APIs
2019Representational State Transfer (REST), an architectural style providing an abstract model of the web, is by far the most popular platform to build web applications. Developing such applications require well-documented interfaces. However, and despite important initiatives such as the Open API Specification, the support for interface description is ...
Vasco T. Vasconcelos +3 more
openaire +1 more source
Test Oracle Generation for REST APIs
ACM Transactions on Software Engineering and MethodologyThe number and complexity of test case generation tools for REST APIs have significantly increased in recent years. These tools excel in automating input generation but are limited by their test oracles, which can only detect crashes, regressions, and violations of API specifications or design best practices. This article introduces AGORA+, an approach
Juan C. Alonso +3 more
openaire +1 more source
In today’s digital landscape, web applications are crucial for user-server inter-actions, with APIs playing a pivotal role. However, ensuring API security is chal- lenging. API security tools require detailed API specifications to effectively identify vulnerabilities.
openaire +1 more source
openaire +1 more source