search

nangtani / blender-addon-tester

The blender addon tester is a test harness to enable pytest hook to allow addons to be tested inside a defined version of blender.
MIT License
64 stars 13 forks source link

test example-from-github-pip #11

Open douglaskastle opened 4 years ago

douglaskastle commented 4 years ago

I am struggling a bit with the test-*-example-from-github-pip.yml. I think it can't work always. Right now it points to a git-repo branch. So that limits other branches from doing iterative work.

When we get pypi support, there will always be a latency issue. Even if published, the module available on pypi might not update for 2 hours, or what ever, so if you have edited a core piece of code you want to test, you might not see it in the length of time it takes for the testing to complete, which looks pretty fast, sub 10 minutes.

This test feels like one that should live with the blender-fake-addon repo, and the other one, with the wheel, lives here.

There is potentially a third/replacement test. One where you just set the PYTHONPATH to the directory with the module lives, or you do a straight python setup install (not with a wheel)

Am I missing something?

myselfhimself commented 4 years ago

Hey this recipe may indeed be strange at first. For the time when the pypi.org project will be set up, that recipe will indeed be meant to keep testing the last stable uploaded online version. So it just tests that installing from pypi.org does work (imagine someone outside of the CI bots pushes broken stuff there), which is non neglectable. But right now, it is basically attempting a remote pip install from a github URL that has no wheel file built. The other recipe does a local pip install from a freshly built wheel file. I do not mind this recipe being either ditched or rename. I personnally have similar recipe on another project and it is like a watcher for me of pypi.org's latest uploaded build's stability. Up to you :)

myselfhimself commented 4 years ago

This could actually be a nigthly jobs that sends us emails if it fails.. Through your travis toolchain could also do that and duplicate work. I do not care much which CI toolchain should prevail.. as long as the project is stable on pypi.org :) and as I can dedicate time building my blender plugin :)