-
Notifications
You must be signed in to change notification settings - Fork 855
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
Implement tests to Music Blocks codebase. #4124
Comments
Jest and Cypress seem like great choices for testing, are we planning to have a specific folder structure for keeping the test files, or will there be a centralised test folder having all the test files? |
I am thinking that the tests could be kept in folders for each subdirectory of the code, e.g. js/utils/tests, js/blocks/tests, etc. |
Could I also contribute to this, @walterbender? |
Anyone/everyone is welcome to contribute. |
I am about to finish musicutils.test.js |
@Commanderk3 I like to collaborate! How do you suggest we move forward. I am also on matrix group? |
Cool @Aman1919 , DM me. User name : Diwangshu Kakoty. |
Hi everyone, I am starting to add tests to platformstyle.js and synthutils.js. Please consider it while picking a file to add tests to so that it doesn't conflict. Thanks! 🙂 |
As per our discussion, we will hold off on DOM-related tests until we sort out some dependency issues. |
I have added test for utils.js...... |
Current Behavior
Currently, we don't have tests in Music Blocks codebase.
Desired Situation
It would be a better idea to include tests in musicblocks codebase for a robust and fast testing workflow so that we don't rely on testing functionalities manually and we avoid breaking changes in production.
In the last meeting, we agreed on using Jest and Cypress to create tests but I am inviting the community to provide their feedbacks on it.
Files to implement tests to (We will keep on adding more files here)
Utils
📚 See contributing instructions.
🙋🏾🙋🏼 Questions: Community Matrix Server.
The text was updated successfully, but these errors were encountered: