vectordotdev / vectordotdev/vector
Full integration tests with `journalctl`
Open
Nobody has claimed this yet.
domain: ci
domain: tests
needs: approval
source: journald
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
After discussing #1544, we discussed the benefits of running full integration tests with journalctl. We should discuss how we can accomplish that in our test suite, or if it makes more sense to run these in the vector test harness.
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
Start by reading issue #1544 and reviewing the existing integration-test setup. Compare whether full journalctl-based tests belong in this repository or the linked vector test harness; the work is complete when the appropriate test location and implementation approach are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- operating-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100