Testing responsibilities #103
Conversation
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
| | **integration** Hub | Hub developers | REST API coverage tests, applications import, [more](https://github.com/konveyor/tackle2-hub/discussions/241) | https://github.com/konveyor/tackle2-hub/... | PR&push (+time anyway?) | | ||
| | **integration** addon-windup | Addon developers | Bash-scripted windup analysis | https://github.com/konveyor/tackle2-addon-windup/blob/main/hack/test-e2e.sh | PR&push (+time anyway?) | | ||
| |||||| | ||
| | **E2E** API | QE&Developers | Golang API test suite (WIP), focusing on sanity checks | https://github.com/konveyor/go-konveyor-tests | time-based schedule | |
There was a problem hiding this comment.
From discussion with @jwmatthews - it might make sense to require a developer responsible for a feature to deliver E2E "sunny day" test to strenghten user focus and E2E responsibility for the feature. (QE should use the provided test as a startingpoint for their scenarios on the feature tests).
There was a problem hiding this comment.
Yes, I'd like to make this a requirement going forward. The idea is we want developers contributing a feature to also contribute an automated means of showing the end-to-end scenario is working as expected.
Signed-off-by: Marek Aufart <[email protected]>
Signed-off-by: Marek Aufart <[email protected]>
|
|
||
| ### Execution and project status | ||
|
|
||
| Konveyor CI repository is https://github.com/konveyor/ci |
There was a problem hiding this comment.
The konveyor/ci repo might not be needed if we put CI/test execution workflow badges to konveyor/tackle2-operator README. (and testing guidelines e.g. to Hub's test README or tackle2-addon)
|
|
||
| | Kind of test | Responsible | Description | Tests code | Trigger (min.required) | | ||
| |---|---|---|---|---| | ||
| | **integration** Hub | Hub developers | REST API coverage tests, applications import, [more](https://github.com/konveyor/tackle2-hub/discussions/241) | https://github.com/konveyor/tackle2-hub/... | PR&push (+time anyway?) | |
There was a problem hiding this comment.
Draft PR with Hub API tests: konveyor/tackle2-hub#268
|
Looks Good @aufi . |
|
I'm going to do a minor update based on CI work from last months to make it up-to-date and ready for review/merge. |
Signed-off-by: Marek Aufart <[email protected]>
|
Updated enhancement with few CI notes and removing not relevant parts. Ready for review. |
Signed-off-by: Marek Aufart <[email protected]>
As a follow-up on #98 "Add CI testing overview" and an exploration on devs&QE cooperation on our recent migration projects, this enhacement attempts to specify expected responsibilities and Konveyor testing work coordination.