appzio/php-sdk

Appzio PHP SDK

Appzio REST bootstrap library

If you have an Appzio app, you will also automatically have an access to the app's own API. Through the api you can create users, manipulate data, access gamification information, access apps configuration and many other things., _(*1)

Appzio's own native iOS and Android apps make use of the very same API, so API is always available and should always pass these basic tests., _(*2)

You can email developer-support at our main domain address for queries., _(*3)

For up-to-date documentation & implementation status: http://appzio.com/, _(*4)

To run the basic tests: 1) comment out the constants from top of the tests/basic.php 2) run this from the command line: phpunit --stderr --bootstrap tests/bootstrap.php tests/basic.php, _(*5)

Test setup 1

Use the provided keys within the basic.php (uncomment first), they connect with app.appzio.com server and tests should run without any errors, _(*6)

Test setup 2

You can create a new app at appzio.com from the included zip-file and configuring the library to use the api keys of the new app., _(*7)

Running the test

If everything works ok, you should be seeing a this kind of output:, _(*8)

phpunit --stderr --bootstrap tests/bootstrap.php tests/basic.php PHPUnit 4.7.7 by Sebastian Bergmann and contributors., _(*9)

........., _(*10)

Time: 7.39 seconds, Memory: 12.00Mb, _(*11)

OK (9 tests, 27 assertions), _(*12)

Errors

If something went wrong, it would look something like this:, _(*13)

Time: 25.93 seconds, Memory: 12.00Mb, _(*14)

There were 2 errors:, _(*15)

1) PHPSDKTestCase::testFbId Undefined property: stdClass::$msg, _(*16)

/Users/trailo/dev/rest-bootstrap-php/tests/tests.php:245, _(*17)

2) PHPSDKTestCase::testFbToken Undefined property: stdClass::$msg, _(*18)

/Users/trailo/dev/rest-bootstrap-php/tests/tests.php:258, _(*19)

FAILURES! Tests: 13, Assertions: 35, Errors: 2., _(*20)

Troubleshooting

Errors can be caused by: - incorrect test app configuration (see the attached app template) - api bugs - incorrect test setups - api incompatibility (shouldn't happen), _(*21)

The test time is a good indication whether everything works as it should. Naturally the speed of your environment affects a lot. Here are couple indicative times for the current version:, _(*22)

Local development environment, debug enabled, with caching: Time: 7.39 seconds, Memory: 12.00Mb, _(*23)

App server, optimum connectivity, server debug disabled, with caching: Time: 21.11 seconds, Memory: 12.25Mb, _(*24)