-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create a testing documentation. #37
Comments
And something we are completely missing: best practices for writing and running javascript unit tests. Ross made Buster.JS integration for zope.testrunner during SeaSprint, but Rok prefers pure javascript-tools. @garbas, how would you integrate plone.mockup tests for Jenkins? |
I created another issue to discuss this: #38 |
are they any news on that, I would like to integrate these docs to docs.plone.org |
I started some kind of docs, but nothing that is ready to include yet: https://github.com/tisto/plone-testing-documentation I will try to work on that during PLOG. I guess it would make sense to include the testing docs into the p.a.testing docs anyways. |
Should pointing to bobtemplates.plone docs be a solution or do we want narrative documentation also? |
We already have https://docs.plone.org/develop/testing/index.html wouldn't that be enough? |
Best practices and examples for unit/integration tests, functional zope.testbrowser and robot framework tests.
The text was updated successfully, but these errors were encountered: