Re: [Dev] EMM Unit test reviewing

2014-07-14 Thread Krishantha Samaraweera
Hi all,

On Tue, Jun 24, 2014 at 6:42 PM, Chan duli...@wso2.com wrote:

 Attendee:- Manuranga, Dulitha, Dilan, Krishantha, Kasun, Inosh,
 Krishanthi, Harshan, Dilshan

- Improve the tier up, tier down functions per test case in jaggery
test
- Integrate to the build (jaggery-test) and Test Automation  Framework


Integration part is done. We have come up with a common test which can use
to run all Jaggery app tests. Changes are available in GIT.

To use this feature you might need to complete the GIT migration first.

Thanks,
Krishantha.


-
- Throw errors rather than handling them
- Coverage for now can be through a GDoc
- ​Use the test automation suites feature (use default user available
in testing)
- Mocking ability for database layer

 Below 2 issues needs to be fixed in jaggery-test

- ​Handle issue in high number of test case execution
- Handle issue in error text displaying in UI

 We will have to migrate to 4.3.0 since our dependencies are in 4.3.0

 ​Cheers~​

 --
 Chan (Dulitha Wijewantha)
 Software Engineer - Mobile Development
 WSO2Mobile
 Lean.Enterprise.Mobileware
  * ~Email   duli...@wso2.com duli...@wso2mobile.com*
 *  ~Mobile +94712112165 %2B94712112165*
 *  ~Website   dulitha.me http://dulitha.me*
 *  ~Twitter @dulitharw https://twitter.com/dulitharw*
   *~Github @dulichan https://github.com/dulichan*
   *~SO @chan http://stackoverflow.com/users/813471/chan*




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] EMM Unit test reviewing

2014-06-24 Thread Harshan Liyanage
Hi,

Jasmine test framework already has *beforeEach*  *afterEach*  as TearUp 
TearDown functions. This can be used in Jaggery-Test framework. But there
is an issue which causes beforeEach  afterEach functions to be executed
multiple times when the test page is loaded or refreshed. sometimes the
test page becomes non-responsive due to this issue.  I think we need to
address this issue also.

For the mocking purposes we can use *Spies* in Jasmine framework which
can stub any function. For more info please refer to Jasmine documentation
http://jasmine.github.io/2.0/introduction.html.

Thanks,

Best Regards,

Lakshitha Harshan
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com http://wso2.com/*
lean.enterprise.middleware.


On Tue, Jun 24, 2014 at 6:42 PM, Chan duli...@wso2.com wrote:

 Attendee:- Manuranga, Dulitha, Dilan, Krishantha, Kasun, Inosh,
 Krishanthi, Harshan, Dilshan

- Improve the tier up, tier down functions per test case in jaggery
test
- Integrate to the build (jaggery-test) and Test Automation  Framework
- Throw errors rather than handling them
- Coverage for now can be through a GDoc
- ​Use the test automation suites feature (use default user available
in testing)
- Mocking ability for database layer

 Below 2 issues needs to be fixed in jaggery-test

- ​Handle issue in high number of test case execution
- Handle issue in error text displaying in UI

 We will have to migrate to 4.3.0 since our dependencies are in 4.3.0

 ​Cheers~​

 --
 Chan (Dulitha Wijewantha)
 Software Engineer - Mobile Development
 WSO2Mobile
 Lean.Enterprise.Mobileware
  * ~Email   duli...@wso2.com duli...@wso2mobile.com*
 *  ~Mobile +94712112165 %2B94712112165*
 *  ~Website   dulitha.me http://dulitha.me*
 *  ~Twitter @dulitharw https://twitter.com/dulitharw*
   *~Github @dulichan https://github.com/dulichan*
   *~SO @chan http://stackoverflow.com/users/813471/chan*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev