mattermost / mattermost/mattermost-plugin-github
Setup E2E testcases for GitHub plugin
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 179
- Forks
- 180
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
I'm hesitant to merge a PR without proper tests. It creates technical debt and reduces the quality of the code.
I would love to see if we can take more time to write good tests for plugins. Especially Go E2E are quite powerful, as they are written in the same language as most of the plugin code and can still cover the perspective of the end user. See https://github.com/mattermost/mattermost-plugin-msteams/pull/458 as an example.
cc @wiggin77
_Originally posted by @hanzei in https://github.com/mattermost/mattermost-plugin-github/pull/886#discussion_r2026958518_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reviewing the GitHub plugin and the referenced mattermost-plugin-msteams PR for its Go E2E testing approach, then identify the plugin behavior to cover and define completion as a working E2E test suite that exercises it from the end-user perspective.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100