-
Notifications
You must be signed in to change notification settings - Fork 348
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
Unit Testing #23
Comments
I think testing the CSS and HTML output is something that can only done manually. But testing the Navbar extension (if it still exists), and the Configuration is something that should be automatically tested. Testing the container configuration can actually be done very easily with. |
Yes thought so too thanks for the link! |
Might we use the DomCrawler to check for certain classes and number of classes when forms are rendered? Could also check on erroneous forms that the error messages showed up as well. |
we could. |
#956 introduced a new TypeTest i think for others relying on us thats a step forward we could and should probably add more tests for us, but i think thats not as urgent as other things |
Gonna close this. We still need more tests but at least we have some now! |
yehaw ! |
Hi folks, do you have any idea how to ahieve unittesting the best way for this bundle?
i could of course do string comparison for input output, but i am atm not sure if thats a nice way.
Maybe it is cause markup shouldnt change, css might.
But i would like to have some input.
Cheers Phil
The text was updated successfully, but these errors were encountered: