Document test strategy

[strekm]

Description

Based on internal alignement create documentation explaining approach to testing API Gateway Module. GH Workflow names and files convention should be also documented in test strategy. Names and files should follow rules:

• all workflows that run before merge should be prefixed with pull
• all workflows triggered after merge should be prefixed with post
• all workflows running on schedule should be prefixed with schedule
• all workflows related to release should be prefixed with release
• all workflow_call files will be prefixed with call

Reasons

Transparent test strategy

PRs

• Testing strategy for Istio module #1176

ACs [PO]

• test strategy documented

DoD [Developer & Reviewer]

- [ ] Provide unit and integration tests.

• Provide documentation.
  - [ ] Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
  - [ ] If you changed the resource limits, explain why it was needed.
  - [ ] If the default configuration of Istio Operator has been changed, you performed a manual upgrade test to verify that the change can be rolled out correctly.
  - [ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
  - [ ] Add release notes.

Attachments

• part of: Simplified GH Workflows #1162