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

Unit testing #10

Open
ly29 opened this issue Nov 22, 2015 · 2 comments
Open

Unit testing #10

ly29 opened this issue Nov 22, 2015 · 2 comments

Comments

@ly29
Copy link
Contributor

ly29 commented Nov 22, 2015

It was always something we wanted to do to the old Sverchok but it was hard for series of reasons and we never did put the time into it.

But since we are starting over I think it also a good thing to consider.

For example:

  • taking a node layout and duplicating and verifying the resulting layout dict matches,
  • some test layout is some different nodes against an expected result.
  • node functions

Just running every node is worth a great deal as we have recently seen. I have no real experience how to set it up and this is a topic that will need some work, for now just raising the topic. Of course some issues with interaction with blender etc might no be possible to test.

https://docs.python.org/3/library/unittest.html

@zeffii
Copy link
Contributor

zeffii commented Nov 22, 2015

Yes! It's worth trying to have a notion of testing in the back of the mind as these nodes start to become more numerous.

@ly29
Copy link
Contributor Author

ly29 commented Nov 22, 2015

Exactly which is why it is important to start early

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

No branches or pull requests

2 participants