+ .. code-block:: xml
+
+ <dependency>
+ <groupId>org.onap.cps</groupId>
+ <artifactId>cps-ncmp-rest-stub-service</artifactId>
+ <version>VERSION</version>
+ </dependency>
+
+ Replace ``VERSION`` with the actual version number.
+
+2. **Using Custom Response Objects:**
+
+ If you prefer to use custom response objects instead of the built-in ones, follow these steps:
+
+ Modify the `application.yaml` file located in your project's test resources directory (`src/test/resources`).
+
+ Add the following property to the `application.yaml` file, specifying the directory that contains your custom response objects:
+
+ .. code-block:: yaml
+
+ stub:
+ path: "/my_custom_stubs/"
+
+ **Note:** Custom response objects can be placed in the `src/test/resources` directory of your project under the directory defined in above property. Refer to the `examples <https://github.com/onap/cps/tree/master/cps-ncmp-rest-stub/cps-ncmp-rest-stub-service/src/main/resources/stubs>`_ included in the CPS source repository for reference.
+
+3. **Simple Test Code:**
+
+ You may refer to the sample test code 'SampleCpsNcmpClientSpec.groovy' in the local CPS project under the following directory:
+
+ ::
+
+ /cps/cps-ncmp-rest-stub/cps-ncmp-rest-stub-service/src/test/groovy/org/onap/cps/ncmp/rest/stub/
+
+ Alternatively, you can refer to the `example <https://github.com/onap/cps/tree/master/cps-ncmp-rest-stub/cps-ncmp-rest-stub-service/src/test/groovy/org/onap/cps/ncmp/rest/stub>`_ included in the CPS source repository.
+
+**Custom Responses for Supported Endpoints**
+
+ Only the following endpoints are supported for the first draft. To use your custom response objects for these endpoints, create the corresponding JSON files:
+
+ - For RequestMethod.GET /v1/ch/{cm-handle}/data/ds/{datastore-name}, create "passthrough-operational-example.json".
+
+ - For RequestMethod.POST /v1/ch/searches, create "cmHandlesSearch.json".