diff --git a/sections/experimentresults.tex b/sections/experimentresults.tex index ab20736655feff6bf2c32a5e92ee05991babd45e..3f00a3b07db72245e84f6f2b916ee1930535d644 100644 --- a/sections/experimentresults.tex +++ b/sections/experimentresults.tex @@ -50,7 +50,7 @@ To answer this question, we - test data structure and mapping \\ - request generation \\ - parameter inference \\ -- for future work: more approaches like analysis in RESTler, Constructing Operation Dependency Graph in RESTest, precise inference with stemming algor\\ +- for future work: more approaches like analysis in RESTler, Constructing Operation Dependency Graph in RESTest, precise inference with stemming algor -> conclusion\\ - \\ - \\ diff --git a/sections/relatedwork.tex b/sections/relatedwork.tex index 61ae696c09865d5c4046fddf300504ba277fd19f..64add1041749ca2ab63aa16dd6a3cae0864b731d 100644 --- a/sections/relatedwork.tex +++ b/sections/relatedwork.tex @@ -1,4 +1,4 @@ -\chapter{Related Work}\label{ch:relatedwork} +\chapter{Literatures}\label{ch:literatures} There are already many approaches suggesting to test REST APIs with OpenAPI specifications automatically. Mostly, they are black-box approaches where an access to a source code is irrelevant and use Fuzzing [2] - [6]. Fuzzing is sending unexpected, random data or data providing errors into input interfaces and observing if interfaces are stable and provide expected responses. There is also a white box approach [11] which is not the main research target of this paper, but still an interesting way. \\ This section introduces which approaches have been released so far, how they work and which did they achieve.