It is inside this instance of blender that the addon under test gets installed.īlender-addon-tester can be install from pypi: blender-addon-tester is install to the system python and is used to call different versions of blender. It can be confusing with blender as it has an internal version of python that is different from the system python. There is currently support for both Github Actions and Travis CI. They can be run against a continous integration tool. Once the addon has been completed and the tests have been written, they are checked in to github.
These tests are written in the pytest format. It will execute a series of tests, by default, located in the tests directory. It will install the addon under test into a location accessible by the respective version of blender. It will download and maintain different versions of blender locally. This python module allows command line pytesting to be performed on different versions of blender. Used to assess comprehensivness of the tests.
Plugs into a continuous integration tool, i.e.Used an industry standard of testing, i.e.Allows an addon to be tested against multiple versions of blender and multiple OSs (ubuntu, windows and macosx).Some parts of the exposed API were radically different and it broke a lot of addons.Ī major effort was put into rework thes addons to get them working again, but the exercise merely highlighted that there is no native testing environment that: This was seen a lot when blender made a upgrade move from 2.79 to 2.80. After a while it is not uncommon for an addon to stop working. However as time pass the, blender releases new versions, adding to and deprecrating parts of the exposed API. Typically an addon will be released and it will be working with the version of blender that is on release at that time. The 3D tool, Blender, allows its functionality to be extended, using python.
0 kommentar(er)
