Rephrase E2E, Performance, and Visual test sections #13
Conversation
|
@droguljic can you please add someone from the QA team as a Reviewer? I don't see anyone on the list, and as I can see, you have permission to add them. |
| backend systems or environments. | ||
| - Run tests in parallel and isolate them from external dependencies to improve | ||
| speed and reliability. | ||
| - Automate E2E tests in your CI/CD pipeline to catch regressions early in the |
There was a problem hiding this comment.
Any ideas on what to suggest to devs when to execute E2E tests?
Every PR/every commit/every release?
There was a problem hiding this comment.
We already discussed this, and I don't think we have a good recipe for that. It depends on the project, the architecture, the process, as well as the team itself. I would rather leave it up to the team to choose.
There was a problem hiding this comment.
Maybe we can make a few examples once we start to work on the examples section, with explained advantages and disadvantages for each individual.
There was a problem hiding this comment.
@bubafinder @MiroDojkic I think the best solution here is to write a section on actually automating automation tests. It can (should) be a separate PR and I think we should ask for the whole team input and feedback on that PR.
Rephrase E2E, Performance, and Visual test sections with minor changes and mostly extend the
AntipatternsandBest practicessections.