How to test a blender call when using blender as a module

Building Blender
1

We have a simple class that does this:

...
   bpy.ops.import_scene.gltf(filepath="path_to_file"))
   bpy.ops.wm.save_as_mainfile(filepath="path_to_saved_file")
...

I want to test that we have called the proper functions with the proper names.
I do not seem to find a way to do that.

We are using purest.

with mocker.patch("bpy.ops.wm.save_as_mainfile") as mocked:
   ....

Gives me an error:

AttributeError: 'BPyOpsSubMod' object has no attribute 'save_as_mainfile'

My understanding that everything is a plugin and is initialised runtime.
I tried to mock the init function with no luck because you do not know on which object to mock it, and some of them have it private (shock)…

I tried to do maybe to get out the information from the console, but with no luck aswel.

(Pdb) bpy.ops.console.copy()
*** RuntimeError: Operator bpy.ops.console.copy.poll() failed, context is incorrect

What is the proper way to test that a call has been made to blender?

2

I’m guessing this is just not supported, and you’d have to add your own function that you can patch, that then calls the operator.

Operators are not registered as actual Python attributes on this module, they are looked up in the Blender registry of operators whenever a call is made.

3

Can’t we just patch the Blender registry and look at the patch there?

4

That registry is implemented in C and does not involve Python, it’s not practical for a Python testing framework to hook into that.

5

Okay, so what do you suggest?

We just wrap the operators in our code and test it against our code?

6

Yes, that seems the most practical solution.