Hi,
Here is meeting note on $subject and mainly it was to verifies and validate the change(new ideas) that was come across on last meeting (11/26/2013) [1]. and to have open decision for HTML reporter. Firstly verifies and validate on implementation[2]/Arch and REST api[1] of the system - File structure - Fine - URL pattern - Fine, Built and completed as requested[1]. (But new Idea came on the meeting, point 1 But for 1.1V) Demo Coding can found in gitHub[2] Here is *new ideas and few requirements/ concern* came across on the meeting for jaggery test framework, *[Each will have jira that can be monitor (links are give in below of the points)]* *Point One - URL ID* rather than 'test Spec name' (Plan for 1.1V ) Fine to go with URL with describe or name of the 'testSpec' as it much readable for 1.0V (I am planning to make it for 1.0V) - http://localhost:9763/automobileJS/test/car/1 rather passing the name of testSuite in URL as below - http://localhost:9763/automobileJS/test/car/TestSuiteOne Above one seems looking good, But If name (describe get to long) or contain char like '/' will have issues or limitation of the name. Mainly long name make URL looking ugly. [JAGGERY-334 <https://wso2.org/jira/browse/JAGGERY-334>] *Point Two - Simplify execute*.jag Simplify execute for one method example require("test").run(); only line in executer.jag Therefore reporter registering will happen in modules [JAGGERY-335 <https://wso2.org/jira/browse/JAGGERY-335>] *Point Three - Composite Reporter (JSON/HTML) * (Embedding to back end) Report configuration is handle in test module rather than test User. But He can prefer type of result by passing Parameter Such as - http://localhost:9763/automobileJS/test/car/1?resultType=json - http://localhost:9763/automobileJS/test/car/1?resultType=html (or default) So switching or report type will be on URL parameter. (Optional for this as sub point) Later If can try for request type rather parameter looking on agent (1.1V) [JAGGERY-337 <https://wso2.org/jira/browse/JAGGERY-337>] *Point Four - HTML Reporter for test framework* For reporting as HTML page main found three type of ways such as (AJAX/Socket/JasminAPI - Print).We have to pick one, AJAX will be easy for maintains, Jasmine API - print html report concept is about simple UI ( Perform vise good but not much considerable factor upon test framework). Web Sockets are also consider. [JAGGERY-327 <https://wso2.org/jira/browse/JAGGERY-327>] *Point Five - Listing End points (test File URLs) * When you go to URL such 'http://localhost:9763/automobileJS/test/car/1' .It will give report of result(execution of tests will happen) in simple html table with test Specification. This was default test frame work perspective But if you pass http://localhost:9763/automobileJS/test/car/1 with parameter such as 'list' or will list end points There methods were considered such as 'URL parameters', 'requestType (GET/POST)', 'URL' [JAGGERY-336 <https://wso2.org/jira/browse/JAGGERY-336>] Above points are open for decisions, If I am missing any points pls add. Thanks [1] [Meeting Notes] On jaggery Test Framework Review on 11/26/2013 @Arch List [2] https://github.com/Madhuka/jaggery-test-framewrok/tree/m3 <https://github.com/Madhuka/jaggery-test-framewrok/tree/m3>-- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
