On Sun, Dec 1, 2013 at 10:21 PM, Ruchira Wageesha <[email protected]> wrote:
> Just to clarify the stuff, what my concerns were... > >> 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. >>> >> When we are integrating with automation test framework or some other 3rd >> party test framework >> Dynamic id can be issue. (With rest clients) >> > If each test case is given an Id which is generated dynamically, then > > - how will it behave with new test case addition and deletion > - if the ids get changed with above point, then it will be a concern > for the people who want to execute just a specific test cases i.e. they > will have to hard code the id and there is a possibility of getting it > changed. > > Yap, you points are correct, as our last call for this meeting. There for we can go with test-suite name (*describe()*) rather using ID. *it()* can be used as 'Test describe' I will have look on JAGGERY-339, Thanks Since JAGGERY-339 was there, I tried jasmine API and I will go M5 with it, M6 will be using AJAX > Currently I fixed it in M4[3] >> >> >> [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>] >>> >> It is needed and it is almost fixed in M4[3] >> >> >>> >>> >>> *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) >>> >> Rather passing we can have agent to get this, But It have jaggery >> limitation >> It is reported in here [4], This issue and feature in jaggery will be >> blocker. >> We will checking on fixing it depending on time. (from url parameter we >> can achieve this) >> > What I suggested was, rather having a url param, better to handle it > depending on content negotiation headers. > > Also, I have commented on JAGGERY-339. Have a look. > >> >> [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. >>> >> AJAX will be nice But jaggery have limitation[4] on implementing this. It >> is blocker[4] for this point 4 with AJAX >> If it is not solve, we need to go with jasmine API with print >> OR we can go with adding front end JS and css by manually per now (Not >> nice, ) >> > Have a look on JAGGERY-339. > >> >> [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' >>> >> In here requirement change came across >> such as if user move to Dir from URL then it will list testSuite (end >> points/files urls) but no executions (But issue was ,how user can run all >> the test) >> Only test execution happen when URL hit to testSpec file. >> >> Point five requirement change was not confirm so far, >> >> @ Ruchira :If I am miss any thing pls add, >> @Nuwan: Your ideas also important upon on those points, If any pls add >> >> >> >>> [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> >>> >> >> [3] https://github.com/Madhuka/jaggery-test-framewrok/tree/m4 >> [4] https://wso2.org/jira/browse/JAGGERY-339 >> >>> <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/ >>> >> >> >> >> -- >> *Madhuka* Udantha >> Senior Software Engineer >> Development Technologies >> WSO2 Inc. : http://wso2.com >> >> *Mobile*: +94774066336 >> *Blog*: http://madhukaudantha.blogspot.com/ >> > > > > -- > > *Ruchira Wageesha**Associate Technical Lead* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* > > *email: [email protected] <[email protected]>, blog: > ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, > mobile: +94 77 5493444 <%2B94%2077%205493444>* > -- *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
