public ResponseSpecBuilder expectBody(String path, List<Argument> arguments, Matcher<?> matcher) {
    """
	Same as {@link #expectBody(String, org.hamcrest.Matcher)} expect that you can pass arguments to the path. This
	is useful in situations where you have e.g. pre-defined variables that constitutes the path:
	<pre>
	String someSubPath = "else";
	int index = 1;
	expect().body("something.%s[%d]", withArgs(someSubPath, index), equalTo("some value")). ..
	</pre>
	<p/>
	or if you have complex root paths and don't wish to duplicate the path for small variations:
	<pre>
	expect().
	root("filters.filterConfig[%d].filterConfigGroups.find { it.name == 'Gold' }.includes").
	body(withArgs(0), hasItem("first")).
	body(withArgs(1), hasItem("second")).
	..
	</pre>
	<p/>
	The path and arguments follows the standard <a href="http://download.oracle.com/javase/1,5.0/docs/api/java/util/Formatter.html#syntax">formatting syntax</a> of Java.
	<p>
	Note that <code>withArgs</code> can be statically imported from the <code>io.restassured.RestAssured</code> class.
	</p>
	
	@param path    The body path
	@param matcher The hamcrest matcher that must response body must match.
	@return the response specification
	@see #expectBody(String, org.hamcrest.Matcher)
    """
        spec.body(path, arguments, matcher);
        return this;
    }
public ResponseSpecBuilder expectBody(String path, List<Argument> arguments, Matcher<?> matcher) {
        spec.body(path, arguments, matcher);
        return this;
    }
public ResponseSpecBuilder expectBody ( String path , List < Argument > arguments , Matcher < ? > matcher ) { spec . body ( path , arguments , matcher ) ; return this ; }
Same as {@link #expectBody(String, org.hamcrest.Matcher)} expect that you can pass arguments to the path. This
is useful in situations where you have e.g. pre-defined variables that constitutes the path:
<pre>
String someSubPath = "else";
int index = 1;
expect().body("something.%s[%d]", withArgs(someSubPath, index), equalTo("some value")). ..
</pre>
<p/>
or if you have complex root paths and don't wish to duplicate the path for small variations:
<pre>
expect().
root("filters.filterConfig[%d].filterConfigGroups.find { it.name == 'Gold' }.includes").
body(withArgs(0), hasItem("first")).
body(withArgs(1), hasItem("second")).
..
</pre>
<p/>
The path and arguments follows the standard <a href="http://download.oracle.com/javase/1,5.0/docs/api/java/util/Formatter.html#syntax">formatting syntax</a> of Java.
<p>
Note that <code>withArgs</code> can be statically imported from the <code>io.restassured.RestAssured</code> class.
</p>

@param path    The body path
@param matcher The hamcrest matcher that must response body must match.
@return the response specification
@see #expectBody(String, org.hamcrest.Matcher)
Same as { @link #expectBody ( String org . hamcrest . Matcher ) } expect that you can pass arguments to the path . This is useful in situations where you have e . g . pre - defined variables that constitutes the path : <pre > String someSubPath = else ; int index = 1 ; expect () . body ( something . %s [ %d ] withArgs ( someSubPath index ) equalTo ( some value )) . .. < / pre > <p / > or if you have complex root paths and don t wish to duplicate the path for small variations : <pre > expect () . root ( filters . filterConfig [ %d ] . filterConfigGroups . find { it . name == Gold } . includes ) . body ( withArgs ( 0 ) hasItem ( first )) . body ( withArgs ( 1 ) hasItem ( second )) . .. < / pre > <p / > The path and arguments follows the standard <a href = http : // download . oracle . com / javase / 1 5 . 0 / docs / api / java / util / Formatter . html#syntax > formatting syntax< / a > of Java . <p > Note that <code > withArgs< / code > can be statically imported from the <code > io . restassured . RestAssured< / code > class . < / p >