Skip to content

Commit

Permalink
chore: Remove test tools experimental flag (#211)
Browse files Browse the repository at this point in the history
  • Loading branch information
hampuslavin authored Nov 6, 2024
1 parent b3bc7da commit f11942c
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 8 deletions.
8 changes: 1 addition & 7 deletions docs/06-concepts/18-testing/01-get-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,6 @@

Serverpod provides simple but feature rich test tools to make testing your backend a breeze.

:::warning

The test tools is an experimental feature. Experimental features should not be used in production environments, as their stability is uncertain and they may receive breaking changes in upcoming releases.

:::

:::info

For Serverpod Mini projects, everything related to the database in this guide can be ignored.
Expand Down Expand Up @@ -196,7 +190,7 @@ That's it, the project setup should be ready to start using the test tools!
Go to the server directory and generate the test tools:
```bash
serverpod generate --experimental-features=testTools
serverpod generate
```

The default location for the generated file is `test/integration/test_tools/serverpod_test_tools.dart`. The folder name `test/integration` is chosen to differentiate from unit tests (see the [best practises section](best-practises#unit-and-integration-tests) for more information on this).
Expand Down
1 change: 0 additions & 1 deletion docs/06-concepts/19-experimental.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,6 @@ The current options you can pass are:
|:-----|:---|
| **all** | Enables all available experimental features. |
| **inheritance** | Allows using the `extends` keyword in your model files to create class hierarchies.|
| **testTools** | Generates the Serverpod test tools, see the [testing get started page](testing/get-started) for more information.|

## Inheritance

Expand Down

0 comments on commit f11942c

Please sign in to comment.