# Continuous Integration We recommend when writing Secret Contracts to leverage a CI platform to create a continuous integration flow for your contract. The two types of tests to focus on: * Unit Tests - tests that are executed only in the context of the contract itself * Integration Tests - tests that include executing contract flows on a running chain (LocalSecret or Secret testnet) Our platform of choice is GitHub Actions. GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production. Here are examples of how to implement these flows in your own contracts: * Unit Tests - * Integration Tests - \\ Note that in this example the unit test flow executes the main command `make unit-test`, while the integration tests initialize a LocalSecret instance, and execute a Typescript file that handles deployment, initialization and execution of the test logic. You can find that file [here](https://github.com/scrtlabs/SecretJack/blob/master/contract/tests/integration.ts). --- # Agent Instructions: 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: ``` GET https://docs.scrt.network/secret-network-documentation/development/development-concepts/testing/continuous-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.