-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
[PITCH]: Add functional tests #1091
Comments
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Problem
Currently, as we introduce new features and enhancements to AsyncAPI Studio, the risk of inadvertently breaking existing functionalities increases. Manual testing, while essential, is time-consuming, prone to human error, and not scalable as our platform grows in complexity
Solution
We propose the adoption of Cypress, a powerful end-to-end testing framework, to automate our functional testing processes. Cypress offers several advantages
Rabbit holes
Ensure that we are not impacting release time.
Scope
Out of bounds
Success criteria
We have couple of functional (browser) based tests that we can trust and help us speed up development time.
The text was updated successfully, but these errors were encountered: