Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

MAGECLOUD-4655 Update config file extension for Blackfire #5977

Merged
merged 2 commits into from
Nov 12, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions guides/v2.2/cloud/project/project-integrate-blackfire.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,11 +235,11 @@ By simply defining a set of key requests for Blackfire to profile— `/home`, `/

### Writing your first automated tests and scenarios

You can easily write tests and scenarios for Blackfire to execute. Create a `.blackfire.yml` file and store it at your project root directory.
You can easily write tests and scenarios for Blackfire to execute. Create a `.blackfire.yaml` file and store it at your project root directory.

Try adding the following scenarios in the file:

> .blackfire.yml
> .blackfire.yaml

```yaml
scenarios:
Expand All @@ -257,7 +257,7 @@ See the Blackfire documentation on [Writing tests](https://blackfire.io/docs/coo

### Running your tests automatically {#automation}

Once you create and deploy your `.blackfire.yml` file, you can enable Blackfire to run your tests automatically in various ways:
Once you create and deploy your `.blackfire.yaml` file, you can enable Blackfire to run your tests automatically in various ways:

- **Automated builds on Integration**—Whenever you push code on an Integration, Staging, or Production branch, Blackfire automatically runs your tests. You can receive a notification of the results in various ways, such as a commit status level when using GitHub or Bitbucket. See Blackfire notifications.

Expand Down