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

Choose a testing strategy #85

Open
raphaelcruzeiro opened this issue Mar 8, 2014 · 1 comment
Open

Choose a testing strategy #85

raphaelcruzeiro opened this issue Mar 8, 2014 · 1 comment

Comments

@raphaelcruzeiro
Copy link
Owner

Due to the increased complexity of the editor's core and the recent breaks introduced by new bugfixes, it is now time to choose a testing strategy for the project. This task comprises of choosing a test framework and integrating it with the current code base. The documentation should also be updated, instructing the contributors on how to create tests for the new features and bugfixes.

@otaviosoares , we could use your expertise here.

@raphaelcruzeiro raphaelcruzeiro added this to the 0.6 milestone Mar 8, 2014
@ilanbiala
Copy link

Check out gremlins.js, could be useful for random testing to see if things break. It's not a real testing suite though, you'll need something like Mocha, Chai, or something else to run tests that you define.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants