Debugging and Testing PT3

Posted on April 26, 2012

0


Tools such as firebug in mozillae firefox and element inspector in google chrome can be used to debug websites. Screenshot shows AgNetPro web interface being debugged using the inspect element feature in google chrome:

Web interface usability

Screenshot shows how frontlinesms trigger function handles empty request from website:

 

 

Screenshot shows frontlinesms trigger error response in browser:

Screenshot shows response (OK) to user when sending messages from website directly to frontlinesms:

There is a couple loopholes with this method (also see http simplified request post):

1 Message may be forwarded to group that is not intended for

2 Users registration details cannot be forwarded to user automatically as url request will have the default mobile number 000 (might be possible to change)

SHORT TERM FIX: Adapted server to handle request from website – used request module for node to forward registration details to frontlinesms, admin can add user contact details to frontlinesms and add user to default group

LONG TERM: Registation system will be handled through emails.

Screenshot shows response to user when sending messages from website directly to AgNetPro Server:

Screenshot shows different response to user when sending messages from website directly to AgNetPro Server (based on keyword and content):

Advertisements