How to peer review a core web service function: Difference between revisions
From MoodleDocs
Line 7: | Line 7: | ||
Peer-reviewing is about checking all [https://docs.moodle.org/dev/How_to_contribute_a_web_service_function_to_core this list] points. | Peer-reviewing is about checking all [https://docs.moodle.org/dev/How_to_contribute_a_web_service_function_to_core this list] points. | ||
However here are some essential questions that you should be able to answer: | However here are some essential questions that you should be able to answer: | ||
* is this function relevant? | * is this function relevant? Does it make sens to call this function from an external client? Can you think of a use case? Is this function duplicating another web service function? | ||
* are the parameters correct? | * are the parameters correct? Should they be known by external client? Are they well typed in the web service description? | ||
* are the capabilities and other checks respecting 100% the web version? | * are the capabilities and other checks respecting 100% the web version? | ||
* is the code logic matching 100% the web version? At best the code logic should be one core lib call, is it the case? How could we end up to it? | * is the code logic matching 100% the web version? At best the code logic should be one core lib call, is it the case? How could we end up to it? |
Latest revision as of 03:26, 15 August 2012
This page is an help for peer-reviewer. Complete/modify it whenever you feel confuse. No-one else than you is going to do that, share you knowledge.
Who must peer-review a web service function
The component maintainer must peer-review her/his component web service function. Core web service functions require a full understanding of the component.
How to peer-review
Peer-reviewing is about checking all this list points. However here are some essential questions that you should be able to answer:
- is this function relevant? Does it make sens to call this function from an external client? Can you think of a use case? Is this function duplicating another web service function?
- are the parameters correct? Should they be known by external client? Are they well typed in the web service description?
- are the capabilities and other checks respecting 100% the web version?
- is the code logic matching 100% the web version? At best the code logic should be one core lib call, is it the case? How could we end up to it?