chore(docs/examples): Adding GraphQL information #4001
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
danielbdias
approved these changes
Aug 29, 2024
jfermi
reviewed
Aug 29, 2024
|
|
||
| By creating a Tracetest GraphQL test, you will be able to create trace-based assertions to be applied across the entire flow like any other Tracetest test. Not only that but it allows you to mix and match it with your existing Monitors, Test Suites and CI/CD validations. | ||
|
|
||
| Another big benefit of using traces as test specs is that you can: |
There was a problem hiding this comment.
Suggested change
| Another big benefit of using traces as test specs is that you can: | |
| Other impactful benefits of using traces as test specs are: |
jfermi
reviewed
Aug 29, 2024
|
|
||
| Another big benefit of using traces as test specs is that you can: | ||
|
|
||
| - Get faster MTTR for failing performance tests |
There was a problem hiding this comment.
Suggested change
| - Get faster MTTR for failing performance tests | |
| - Faster MTTR for failing performance tests. |
jfermi
reviewed
Aug 29, 2024
| Another big benefit of using traces as test specs is that you can: | ||
|
|
||
| - Get faster MTTR for failing performance tests | ||
| - Assert against the Mutiple Queries and Mutations at once from a single test execution |
There was a problem hiding this comment.
Suggested change
| - Assert against the Mutiple Queries and Mutations at once from a single test execution | |
| - Assert against the Mutiple Queries and Mutations at once from a single test execution. |
jfermi
reviewed
Aug 29, 2024
|
|
||
| - Get faster MTTR for failing performance tests | ||
| - Assert against the Mutiple Queries and Mutations at once from a single test execution | ||
| - Validate functionality of other parts of your system that may be broken, even when the initial request is passing |
There was a problem hiding this comment.
Suggested change
| - Validate functionality of other parts of your system that may be broken, even when the initial request is passing | |
| - Validate functionality of other parts of your system that may be broken, even when the initial request is passing. |
jfermi
reviewed
Aug 29, 2024
|
|
||
| ## Steps | ||
|
|
||
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/) |
There was a problem hiding this comment.
Suggested change
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/) | |
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/). |
jfermi
reviewed
Aug 29, 2024
| ## Steps | ||
|
|
||
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/) | ||
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal |
There was a problem hiding this comment.
Suggested change
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal | |
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal. |
jfermi
reviewed
Aug 29, 2024
|
|
||
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/) | ||
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal | ||
| 3. Update the `.env` file adding a valid set of AWS credentials |
There was a problem hiding this comment.
Suggested change
| 3. Update the `.env` file adding a valid set of AWS credentials | |
| 3. Update the `.env` file adding a valid set of AWS credentials. |
jfermi
reviewed
Aug 29, 2024
| 1. [Install the tracetest CLI](https://docs.tracetest.io/installing/) | ||
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal | ||
| 3. Update the `.env` file adding a valid set of AWS credentials | ||
| 4. Update the `tracetest.provision.yaml` file adding a valid set of AWS credentials |
There was a problem hiding this comment.
Suggested change
| 4. Update the `tracetest.provision.yaml` file adding a valid set of AWS credentials | |
| 4. Update the `tracetest.provision.yaml` file adding a valid set of AWS credentials. |
jfermi
reviewed
Aug 29, 2024
| 2. Run `tracetest configure --server-url http://localhost:11633` on a terminal | ||
| 3. Update the `.env` file adding a valid set of AWS credentials | ||
| 4. Update the `tracetest.provision.yaml` file adding a valid set of AWS credentials | ||
| 5. Run the project by using docker-compose: `docker-compose up -d` (Linux) or `docker compose up -d` (Mac) |
There was a problem hiding this comment.
Suggested change
| 5. Run the project by using docker-compose: `docker-compose up -d` (Linux) or `docker compose up -d` (Mac) | |
| 5. Run the project by using docker-compose: `docker-compose up -d` (Linux) or `docker compose up -d` (Mac). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the graphql docs and recipes
Changes
Fixes
Checklist