getsentry / getsentry/self-hosted

Land initial groundwork for better self-hosted testing infrastructure

Open
#2,529 0 comments 0 reactions 0 assignees View on GitHub
Project
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
15

Description

We should have a good idea of where we want testing for self-hosted to be in our pipeline, and outline a process for devs to write their own tests for self-hosted. The first step here would be to rewrite our entire testing suite in a framework that is more friendly. If we ourselves struggle to write tests here, how can we expect others to willingly shoulder this burden with us?

```[tasklist]
### Tasks
- [ ] rewrite current e2e tests to a more friendly testing framework
- [ ] measure flakiness of self-hosted e2e tests and ensure it is under <10%
- [ ] lay out new groundwork to re-add testing in the deployment pipeline
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.