Hi,


Here is meeting note on $subject and mainly it was about


   - File structure
   - URL pattern
   - Name of testframewrok



*File structure* was changed from last meeting discussion [1]  to below
structure.

(Change is to have .js (javascripte) file rather than .jag (jaggery) file.)





Coffee jaggery app file tree

|

+---controller

|       order.jag

|       payment.jag|

|

+---model

|       orderQuery.jag

|       paymentQuery.jag

|

+---jaggery.conf

|

*\---tests*

    |   index.jag

    |

    +---order

    |       orderspec.js

    |

    \---payment

            orderspec.js







Rather including so called 'excuter.jag' in each test specification need to
have front end controller to handle it.



eg: '{appName}/test/index.jag' will be front end controller



*[New module will be need to write for this, It also located in 'test'
module]*



Therefore 'jaggery.conf' contain change for routing for this test dir (1
line change). In our last(19/11/2013) discussion meeting we plan not to
chnage config. Since new front end controller need this so this change will
be effected.



Secondly we mainly look into *URL pattern* for jaggery test framework

Current URL ::




   - pattern :
   
http://localhost:9763/automobile/test/[{folderName}]*/{file}/?spec=[{testSpecName}]

   - example : 
http://localhost:9763/automobile/test/car/carSpec.jag?spec=upgradeEngineSize



Proposed URL ::




   - pattern :
   
http://localhost:9763/automobile/test[/{folderName}]*/{fileName}[/{testSpecName
}]

   - example : 
http://localhost:9763/automobile/test/car/carSpec/upgradeEngineSize



To make this change we will need to have new routing mechanism and it also
coming under 'test' module some case it will embed into front end
controller. This new routing mechanism will be also developed.



By this time we will need '*Name*' for jaggery test framework

Please feel free to give your idea on name?



**later 'wrapper.js' in test module will have the name TF*



So more with developer aspect view.

When request came to 'http://localhost:9763/automobile/test/[{folderName}]*/'
will require all js in folder can make execution with test frame work.


Here is demo[2] and sample code[3] location for to try out[2]




*If I am missed any points, pls add those. *


[1] Meeting Notes on 11/19/2013:: $Subjected; [Meeting Notes] on jaggery
apps test framework regard architecture

[2] https://github.com/Madhuka/jaggery-test-framewrok/wiki

[3] https://github.com/Madhuka/jaggery-test-framewrok


Thanks
-- 
*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

Reply via email to