# Testing

**Unit Testing**

**Methods in test classes MUST start with “test” then a camelCased name of the test**

Good

`class ExampleTest extends TestCase`

`{`

&#x20;`public function testBasicTest()`

&#x20;`{`

Bad

`class ExampleTest extends TestCase`

`{`

&#x20;`public function test_basic_test()`

&#x20;`{`

**Integration Tests**

*WIP (work in progress): this will be filled up by collected best practices once we had done enough research about the subject matter.*

**Acceptance Tests**

*WIP (work in progress): this will be filled up by collected best practices once we had done enough research about the subject matter.*

**Scalability**

*WIP (work in progress): this will be filled up by collected best practices once we had done enough research about the subject matter.*

**Scaling Up**

*TODO*

**Scaling Out**

*TODO*

**Microservices**

*WIP (work in progress): this will be filled up by collected best practices once we had done enough research about the subject matter.*


---

# 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://sops.larasoft.io/laravel-sops/testing.md?ask=<question>
```

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.
