Loklak provides several APIs which are localhost-only! i.e. only localhost clients are granted access. For example:
This feature makes it difficult to integrate testing of such APIs with the main test-suite. Since we use Travis-CI for online testing, we would have to create an extra connection setup for online testing and offline (localhost) testing.
So in this dilemma, I had to come up with an approach which would allow the test-suite to recognise Travis-CI and take necessary actions to handle such conditions. After some reading, I came across PHP’s
getenv() function which provides information of current environment variables.
So, in order to write tests for localhost-only APIs, I used
getenv() as a check to differentiate between Travis and local tests.
Using this approach, tests for Settings and Accounts API were added. Code samples shown below!
This approach improves the tested code-coverage and integrates all unit tests into one file!
This week, I added tests for
susi APIs and fixed tests for
user topology related queries. PHPUnit was used as the testing framework since it provides code-coverage support.
Loklak PHP API now has a good test-suite support and associated examples to help you use our services
Below are the Tests that were added.
testPush – to test Push API.
testSusi – to test newly added Susi API.
Refer to this and this for more info about
testMap – to test map API.
testMarkdown – to test markdown API.
For more detailed information regarding the entire Loklak PHP API test-suite, refer to this.
In above process, code-coverage was increased from 33% to 61%. Test-suite continuously updated as new APIs are added to Loklak.
Source support for Search API
Apart from that, since Loklak is scaling beyond Twitter.
Source argument has been added to the
search API to define the source of search results. As far as wordpress plugins are concerned, since they only require twitter results for now,
source has been added as a default argument. See below code: