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

[FEATURE]: end-to-end tests #52

Open
shanduur opened this issue Apr 9, 2024 · 1 comment
Open

[FEATURE]: end-to-end tests #52

shanduur opened this issue Apr 9, 2024 · 1 comment
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@shanduur
Copy link
Member

shanduur commented Apr 9, 2024

Are you interested in contributing to the development of this feature?

Yes

Is your feature request related to a problem? Please describe.

Our current testing process lacks comprehensive coverage, particularly in terms of end-to-end testing. This leads to potential issues going unnoticed until later stages of development or even in production.

Describe the solution you'd like.

I would like to implement end-to-end tests to ensure that all components of our application work together as expected. These tests should simulate real user scenarios, covering the entire application workflow from start to finish.

Describe alternatives you've considered.

One alternative is to rely solely on unit tests and integration tests. However, these tests may not capture all possible interactions between components and may miss issues that arise only in the context of the entire application workflow.

Additional Information

End-to-end tests will not only improve the quality of our software but also increase confidence in our releases by catching potential issues earlier in the development process. Additionally, they can serve as living documentation of our application's behavior and help onboard new team members more effectively.

@shanduur shanduur added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 9, 2024
@shanduur shanduur pinned this issue Apr 9, 2024
@mhmxs mhmxs self-assigned this Apr 16, 2024
@mhmxs
Copy link
Contributor

mhmxs commented Apr 16, 2024

There are a few popular test frameworks on the market:
https://github.com/vapor-ware/kubetest - Python based
https://github.com/kubeshop/testkube - Only for testing, supports multiple test tools
https://github.com/tilt-dev/tilt - Mostly a developer tool
https://github.com/kyverno/chainsaw - Only for testing with infra, stand-alone tool, popular at Linode
https://garden.io/ - Supports both dev env, infra and test execution, supports multiple test tools

shanduur added a commit that referenced this issue Apr 26, 2024
## What this PR does / why we need it:
<!--
What code changes are made?
What problem does this PR addresses, or what feature this PR adds?
-->
This change adds Chainsaw to drive E2E testing.

## Which issue(s) this PR resolves:
<!--
Usage: `Resolves #<issue number>`, or `Resolves <link to the issue>`.
If PR is about `failing-tests`, please post the related tests in a
comment and do not use `Resolves`
-->
Resolves # #52

## Special notes for your reviewer:
<!-- Do you think reviewers should focus on any particular parts of
code? -->
<!-- REPLACE WITH CONTENT -->

## Additional documentation e.g., enhancement proposals, usage docs,
etc.:
<!-- This section can be blank if this pull request does not require a
release note. -->
<!-- REPLACE WITH CONTENT -->

---------

Co-authored-by: Richard Kovacs <rkovacs@akamai.com>
Co-authored-by: Mateusz Urbanek <mateusz.urbanek.98@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants