You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
## 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>
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.
The text was updated successfully, but these errors were encountered: