Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(testing-strategy): add testing strategy and test plan documents drafts #306

Merged
merged 6 commits into from
Jul 16, 2024

Conversation

ameteiko
Copy link
Contributor

Description

This PR adds a draft for the testing strategy document along with a test plan template.

@ameteiko ameteiko requested a review from a team as a code owner June 26, 2024 12:44
@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 26, 2024
@ameteiko ameteiko marked this pull request as draft June 26, 2024 12:44
@kyma-bot kyma-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 26, 2024
@tmilos77 tmilos77 added this to the Cloud Manager GA v1.0 milestone Jul 15, 2024
@ngrkajac ngrkajac marked this pull request as ready for review July 15, 2024 12:15
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 15, 2024
@ngrkajac ngrkajac requested a review from a team July 15, 2024 12:16
| Compatibility | Degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions while sharing the same common environment and resources. | To define a comprehensive set of compatibility requirements, we need a centralised systems engineering approach and guidelines for the interconnection and integration of Kyma components. |
| Interaction Capability | Degree to which a product or system can be interacted with by specified users to exchange information ia the user interfaceto complete specific tasks in a variety of contexts of use. | We need to create a centralised Kyma user guide focused on user-friendliness and user engagement first. |
| Security | Degree to which a product or system defends against attack patterns by malicious actos and protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorisation. | We need a stakeholder to define the security expectations and to provide the testing scenarios for the different security aspects. |
| Flexibility | Degree to which a product can be adapted to changes in its requirements, contexts of use or system environment. This characteristic is composed of the adaptability, scalability and installability. | These quality characteristics are the higher-level test suites compared to the performance efficiency ones and will be added gradually. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Flexibility | Degree to which a product can be adapted to changes in its requirements, contexts of use or system environment. This characteristic is composed of the adaptability, scalability and installability. | These quality characteristics are the higher-level test suites compared to the performance efficiency ones and will be added gradually. |
| Flexibility | Degree to which a product can be adapted to changes in its requirements, contexts of use, or system environment. This characteristic is composed of adaptability, scalability, and installability. | These quality characteristics are the higher-level test suites compared to the performance efficiency ones and will be added gradually. |

| System integration test report | System analysis and software design | |
| Integration test report | Testing the interconnection of the <...> components | |
| Code coverage report | Unit tests | Unit testing test plan |
| Code coupling report | Codebase mainatainability | Maintainability test plan |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Code coupling report | Codebase mainatainability | Maintainability test plan |
| Code coupling report | Codebase maintainability | Maintainability test plan |

Co-authored-by: Małgorzata Świeca <[email protected]>
@tmilos77 tmilos77 requested a review from mmitoraj July 16, 2024 11:49
@kyma-bot kyma-bot added the lgtm Looks good to me! label Jul 16, 2024
@kyma-bot kyma-bot merged commit f550578 into kyma-project:main Jul 16, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants