The generated binding API is generated by looking at the API reference page and the header of the SDK rootstrap.
Most of it is scripted, but we currently have no steps to verify this.
(Since tizen_interop is a binding for an already published API, there is no need to verify the API operation.)
We need unit tests for the codes implemented in symgen, tizen_interop, and tizen_interop_callbacks, and I think we need to make some code(api or mock...) that can be called & tested in a headless environment.
The generated binding API is generated by looking at the API reference page and the header of the SDK rootstrap.
Most of it is scripted, but we currently have no steps to verify this.
(Since tizen_interop is a binding for an already published API, there is no need to verify the API operation.)
We need unit tests for the codes implemented in symgen, tizen_interop, and tizen_interop_callbacks, and I think we need to make some code(api or mock...) that can be called & tested in a headless environment.