On Thu, Apr 24, 2014 at 2:37 PM, Krishantha Samaraweera <[email protected] > wrote:
> Any particular reason for making Jaggery directory structure differ from > normal carbon directory structure? > decision can be found in here[1]. Simple change is that jaggery root have dir called 'carbon' there you can find normal wso2 product directory structure > We can make it configurable, however we need to introduce this > configuration to all product test modules. Another alternative would be to > change jar instrumentation logic to find plugins directory first, and > construct the path. We will fix this and let you know. > > Please raise a TA JIRA for this. > done, TA-827[2] Thanks [1] [Architecture] Jaggery distribution structure [2] https://wso2.org/jira/browse/TA-827 > > Thanks, > Krishantha. > > > On Thu, Apr 24, 2014 at 1:58 PM, Madhuka Udantha <[email protected]> wrote: > >> Hi, >> >> I found the cause for the failure. It is about jaggery file structure >> >> By debugging automation.engine [CodeCoverageUtils (line 136)] Where try >> to access \plugins. jaggery file structure bit different[2] to other wso2 >> products[1]. Jaggery have extra directory called carbon and it is missing >> in CodeCoverageUtils.java. >> >> So we will need some fix for this where we can pass it from configuration >> or looking on server name or type to define file/path structure. >> >> >> [1] >> F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\repository\components\plugins >> [2] >> F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\ >> *carbon*\repository\components\plugins >> >> >> >> On Thu, Apr 24, 2014 at 1:08 PM, Krishantha Samaraweera < >> [email protected]> wrote: >> >>> Hi Dharshana, >>> >>> The startup script naming problems if fixed already - [1]. So the >>> problems is not with startup script name. >>> >>> [1]https://wso2.org/jira/browse/TA-825 >>> >>> Thanks, >>> Krishantha. >>> >>> >>> On Thu, Apr 24, 2014 at 11:43 AM, Dharshana Warusavitharana < >>> [email protected]> wrote: >>> >>>> Hi Madhuka, >>>> >>>> Please refine the instrumentation jars listed in intrumentation.txt. >>>> Seems like the jar files which are listed to be instrument were not present >>>> in the pack. >>>> >>>> Id the startup script is different that will be the next point. >>>> >>>> For that you can have your own server startup module and add it as an >>>> extensible module to the framework. >>>> >>>> You can refer [1] to write a extensible module for the framework. >>>> >>>> [1]. https://docs.wso2.org/display/TA430/Pluggable+Module+Executors >>>> >>>> Thank You, >>>> Dharshana. >>>> >>>> >>>> >>>> >>>> On Thu, Apr 24, 2014 at 11:10 AM, Madhuka Udantha <[email protected]>wrote: >>>> >>>>> Getting error start carbon server from test-automation-framework >>>>> Since jaggery have different name for server starting script. was it >>>>> the issue? >>>>> or is there any config need to added? >>>>> >>>>> I have updated below repo and built. >>>>> >>>>> - carbon-platform-integration >>>>> - carbon-platform-integration-utils >>>>> >>>>> >>>>> >>>>> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ >>>>> org.jaggeryjs.integration.tests --- >>>>> [INFO] Surefire report directory: >>>>> F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\surefire-reports >>>>> >>>>> ------------------------------------------------------- >>>>> T E S T S >>>>> ------------------------------------------------------- >>>>> Running TestSuite >>>>> Extracting carbon zip file.. >>>>> Carbon Home - >>>>> F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp1398317632682\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT >>>>> Instrumentation of jar files in progress ... >>>>> Fail to start carbon server >>>>> java.lang.NullPointerException >>>>> at >>>>> org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrumentSelectedFiles(CodeCoverageUtils.java:140) >>>>> at >>>>> org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrument(CodeCoverageUtils.java:108) >>>>> at >>>>> org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerManager.startServerUsingCarbonHome(CarbonServerManager.java:71) >>>>> at >>>>> org.wso2.carbon.integration.common.extensions.carbonserver.TestServerManager.startServer(TestServerManager.java:102) >>>>> at >>>>> org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:49) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at >>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>> at >>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>> at >>>>> org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:73) >>>>> at >>>>> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:48) >>>>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1032) >>>>> at org.testng.TestNG.run(TestNG.java:983) >>>>> at >>>>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) >>>>> at >>>>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) >>>>> at >>>>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at >>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>> at >>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>> at >>>>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) >>>>> at >>>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) >>>>> at >>>>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) >>>>> at >>>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) >>>>> at >>>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) >>>>> >>>>> -- >>>>> *Madhuka* Udantha >>>>> Senior Software Engineer >>>>> Development Technologies >>>>> WSO2 Inc. : http://wso2.com >>>>> >>>>> *Mobile*: +94774066336 >>>>> *Blog*: http://madhukaudantha.blogspot.com/ >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Dharshana Warusavitharana >>>> Senior Software Engineer , Test Automation >>>> WSO2 Inc. http://wso2.com >>>> email : [email protected] <[email protected]> >>>> Tel : +94 11 214 5345 >>>> Fax :+94 11 2145300 >>>> cell : +94772202595 >>>> blog : http://dharshanaw.blogspot.com >>>> >>>> lean . enterprise . middleware >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Krishantha Samaraweera >>> Senior Technical Lead - Test Automation >>> Mobile: +94 77 7759918 >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middlewear. >>> >> >> >> >> -- >> *Madhuka* Udantha >> Senior Software Engineer >> Development Technologies >> WSO2 Inc. : http://wso2.com >> >> *Mobile*: +94774066336 >> *Blog*: http://madhukaudantha.blogspot.com/ >> > > > > -- > Krishantha Samaraweera > Senior Technical Lead - Test Automation > Mobile: +94 77 7759918 > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middlewear. > -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
