> For the complete documentation index, see [llms.txt](https://accelchain.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://accelchain.gitbook.io/docs/test.md). # Test Accelchain prioritizes the security of smart contracts through a comprehensive testing framework. Testing begins at the compiler level, where our built-in setup identifies basic Solidity errors directly within the IDE. Users can manually rectify inline errors or leverage our 'Ask AI' feature for remediation assistance. For manual testing, Accelchain creates a local instance of the contract, akin to Remix. This allows users to meticulously examine and test contract outputs, ensuring the correct functionality of their smart contracts. Developers have direct control and visibility into the local environment to facilitate thorough manual testing. For automatic validation, Accelchain's background tools execute symbolic execution on contracts to automatically validate that functions operate as intended. This automated process enhances the efficiency of testing, ensuring a robust and secure foundation for smart contracts on the Accelchain platform. --- # 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://accelchain.gitbook.io/docs/test.md?ask=&goal= ``` `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.