> For the complete documentation index, see [llms.txt](https://open.kingdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open.kingdata.com/how-to-develop-an-indicator/step5-test-and-pull-request.md).

# Step5: Test and Pull Request

So far we have completed all the work that needs to be opened for an indicator. Next, we test our crawler and submit a pull-request.

## Test Our Crawler

Change to the root directory of the project

```shell
$ scrapy crawl idx-contract-position-ratio
```

`idx-contract-position-ratio` is the name of the crawler, which we defined in the code.

{% hint style="success" %}
If the corresponding template  content can be printed normally according to our expectations, the test is passed
{% endhint %}

## Pull Request

The only thing to do next is to submit a pull-request on Github, and then wait for the review of the staff.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://open.kingdata.com/how-to-develop-an-indicator/step5-test-and-pull-request.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.