-
Notifications
You must be signed in to change notification settings - Fork 83
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
Add Testing Framework #186
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #186 +/- ##
=======================================
Coverage ? 43.82%
=======================================
Files ? 14
Lines ? 1887
Branches ? 0
=======================================
Hits ? 827
Misses ? 1060
Partials ? 0 ☔ View full report in Codecov by Sentry. |
Using more robust testing in #186 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So far I have been slack on introducing formal unit testing & CI, as it's slightly more complex when having to try and test inside of Blender, which is a desktop app and not a installable package.
I have found the
blender-addon-tester
which aims to solve such a problem by scraping the Blender downloads page for relevant versions, downloading them then running Blender in the headless mode to run variouspytest
tests.Certainly the import code should be able to be tested with this method, and reported on with
pytest
. The testing of the internal nodes will be slightly more difficult. In conversation with Blender devs, saving a 3D model and comparing it to a previously created 3D model is their method of testing the nodes, so potentially will try and set up something along those lines..gltf
is likely the model of choice.This PR introduces the testing framework, which I am looking to add some more initial tests to in the coming weeks.