Hi,
I was using Jaggery Editor (In Devs) for few days as it was been released. and It was good experience and it is good editor. I notice some bugs. 1. Whenever I was creating jaggery project with existing location. As I open jaggery app from DevS It will remove jaggery.conf and index.jag in root level of the application and default template files (Critical issue as I see) 2. Syntax error such as passing json as argument into function rather passing as variable (simple bugs) 3. Auto completion for jaggery keywords (second level auto Completion) 4. issues with code formatting Created jira issues under jaggery IDE component. Thanks On Thu, Nov 21, 2013 at 8:43 PM, Viraj Rajaguru <vi...@wso2.com> wrote: > Hi, > > >>>>> I was looking for auto tests, becuase, it is hard to test them all >>>>> manually. >>>>> >>>>> Alternatively, we can see if we can use ESB auto tests in here, where >>>>> we develop the artifacts for all mediators using DevS and test those >>>>> artifacts with ESB auto test framework. That could work. >>>>> >>>> > +1 > > And also, > > Until we complete the full automate tests (open up the editor, drag & drop > mediators, delete some mediators from the flow, going to source view, edit > the source view, come back to design view etc..) in a proper manner for ESB > Graphical editor using SWTBot, we can use SWTBot in some other way to test > the ESB Graphical editor to some extend. > > We can use SWTBot to do following simple steps. > > 1. Open up the graphical editor. Go to source view. > 2. Copy and paste a valid configuration (previously defined proxy service, > sequence etc.. with mediators that we want to test) > 3. Come back to the design view. Save the diagram. > 4. Go back to the source editor. > > Then we can compare the configuration in the editor with the initial > configuration which we provided for editor. If these two configurations are > identical we can say that test is pass for that configuration otherwise it > is not. > > Since we are triggering both seralization and deseralization (source > generating & reverse engineering) logic in above steps we can guarantee > that functionality of the mediators inside provided configuration is not > broken. We can run this test against set of predefined configuration to > cover all the mediators, endpoints etc.. > > > Thanks, > Viraj. > > > >> >>>> Yes.. +1 >>>> >>>> We can produce CAR files with all mediator scenarios and provide them >>>> to ESB Testing Framework which could show us the error in configurations. >>>> Also once we are done with it, the same CAR files can be used for future >>>> ESB testing as well. >>>> >>>> We will execute that plan for the release. Thanks for the valuable >>>> input Samisa. >>>> >>>> Best Regards, >>>> Harshana >>>> >>>>> >>>>> >>>>> Thanks, >>>>> Samisa... >>>>> >>>>> >>>>> Samisa Abeysinghe >>>>> >>>>> Vice President Training >>>>> >>>>> WSO2 Inc. >>>>> http://wso2.com >>>>> >>>>> >>>>> >>>>> On Thu, Nov 21, 2013 at 2:27 PM, Harshana Martin <harsh...@wso2.com>wrote: >>>>> >>>>>> Hi Samisa, >>>>>> >>>>>> >>>>>> On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe >>>>>> <sam...@wso2.com>wrote: >>>>>> >>>>>>> What is the plan to test all mediators for basic functionality for >>>>>>> 3.3.0? >>>>>>> >>>>>> >>>>>> At the moment we are planning to test the mediators using the samples >>>>>> mainly and some known use cases. >>>>>> >>>>>>> >>>>>>> I understand that some mediators were badly broken in 3.2.0 release >>>>>>> e.g. XACML. >>>>>>> >>>>>> >>>>>> Although Entitlement mediator was a specific mediator only, we fixed >>>>>> but there could be some other mediators like that. So we are going to >>>>>> cover >>>>>> all most all mediators during the testing. >>>>>> >>>>>>> >>>>>>> Can we make use of the auto test framework to ensure that there are >>>>>>> no absolute blockers in any mediator out of the full mediator lot. >>>>>>> >>>>>> >>>>>> Test framework is still not developed to support that level of >>>>>> requirements. We will try to improve it while testing the 3.3.0. But most >>>>>> of the testing will happen manually for this release. We are planning to >>>>>> assign someone full-time basis to improve the test framework to support >>>>>> complete automated testing. >>>>>> >>>>>> Thanks and Regards, >>>>>> Harshana >>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Samisa... >>>>>>> >>>>>>> >>>>>>> Samisa Abeysinghe >>>>>>> >>>>>>> Vice President Training >>>>>>> >>>>>>> WSO2 Inc. >>>>>>> http://wso2.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Nov 18, 2013 at 3:49 PM, Asanka Sanjeewa >>>>>>> <asan...@wso2.com>wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> We have WSO2 Developer Studio 3.3.0 Alpha 3 version ready to be >>>>>>>> downloaded at [1]. Installed eclipse distributions available at [2]. >>>>>>>> >>>>>>>> This release includes following new feature, improvements and bug >>>>>>>> fixes. >>>>>>>> >>>>>>>> New Feature >>>>>>>> >>>>>>>> - [TOOLS-1855 <https://wso2.org/jira/browse/TOOLS-1855>] - >>>>>>>> Cloud connector support >>>>>>>> >>>>>>>> Improvements >>>>>>>> >>>>>>>> - [TOOLS-1870 <https://wso2.org/jira/browse/TOOLS-1870>] - >>>>>>>> Enabling Jaggery Editor Auto-Complete even without typing a >>>>>>>> character >>>>>>>> - [TOOLS-2085 <https://wso2.org/jira/browse/TOOLS-2085>] - >>>>>>>> There is no way to rename a GReg artifact. >>>>>>>> - [TOOLS-2106 <https://wso2.org/jira/browse/TOOLS-2106>] - >>>>>>>> Adding perspective login change icon into toolbar >>>>>>>> - [TOOLS-2107 <https://wso2.org/jira/browse/TOOLS-2107>] - >>>>>>>> Login window should not pop-up when resetting the perspective and >>>>>>>> should >>>>>>>> pop-up for new perspective Only >>>>>>>> >>>>>>>> Bug Fixes >>>>>>>> >>>>>>>> - [TOOLS-1337 <https://wso2.org/jira/browse/TOOLS-1337>] - >>>>>>>> There is no way to add "include" block inside Script Mediator >>>>>>>> - [TOOLS-1694 <https://wso2.org/jira/browse/TOOLS-1694>] - AF >>>>>>>> perspective detais view not filling all the feilds >>>>>>>> - [TOOLS-1719 <https://wso2.org/jira/browse/TOOLS-1719>] - [Dev >>>>>>>> Studio-3.2] - Logging not consistent with WSO2 Standards >>>>>>>> - [TOOLS-1722 <https://wso2.org/jira/browse/TOOLS-1722>] - Dev >>>>>>>> Studio fails to create Registry resource without file extension >>>>>>>> - [TOOLS-1731 <https://wso2.org/jira/browse/TOOLS-1731>] - Dev >>>>>>>> Studio fails to rename a resource correctly. >>>>>>>> - [TOOLS-1737 <https://wso2.org/jira/browse/TOOLS-1737>] - [Dev >>>>>>>> Studio 3.2] End Point Connection Issues >>>>>>>> - [TOOLS-1738 <https://wso2.org/jira/browse/TOOLS-1738>] - [Dev >>>>>>>> Studio 3.2] - Null Argument error for Clone Mediator >>>>>>>> - [TOOLS-1743 <https://wso2.org/jira/browse/TOOLS-1743>] - [Dev >>>>>>>> Studio 3.2] - Exceptions Creating EndPoint (JMS) >>>>>>>> - [TOOLS-1746 <https://wso2.org/jira/browse/TOOLS-1746>] - [Dev >>>>>>>> Studio-3.2] - Argument not valid Exception in Opening with Registry >>>>>>>> Info >>>>>>>> Editor >>>>>>>> - [TOOLS-1747 <https://wso2.org/jira/browse/TOOLS-1747>] - [Dev >>>>>>>> Studio-3.2] -Edit and saving "resources" to registy not possible >>>>>>>> - [TOOLS-1757 <https://wso2.org/jira/browse/TOOLS-1757>] - >>>>>>>> Create new Axis2 Service Project -> wrong directory >>>>>>>> - [TOOLS-1945 <https://wso2.org/jira/browse/TOOLS-1945>] - NPE >>>>>>>> when trying to run ELB 2.0.2 from Dev Studio >>>>>>>> - [TOOLS-1948 <https://wso2.org/jira/browse/TOOLS-1948>] - When >>>>>>>> A/F login failed there is no way to re-login wihtout closing it >>>>>>>> - [TOOLS-1951 <https://wso2.org/jira/browse/TOOLS-1951>] - >>>>>>>> Trying to get versions from A/F application with just a developer >>>>>>>> role >>>>>>>> throws an Internal Error >>>>>>>> - [TOOLS-1952 <https://wso2.org/jira/browse/TOOLS-1952>] - >>>>>>>> Updating an app with Data Sources throws an error >>>>>>>> - [TOOLS-1975 <https://wso2.org/jira/browse/TOOLS-1975>] - Esb >>>>>>>> graphical editor allows to delete proxy service >>>>>>>> - [TOOLS-1976 <https://wso2.org/jira/browse/TOOLS-1976>] - When >>>>>>>> pasted or moved a artifact between folders the artifact.xml doesn't >>>>>>>> updated >>>>>>>> corectly >>>>>>>> - [TOOLS-1996 <https://wso2.org/jira/browse/TOOLS-1996>] - >>>>>>>> Error occurs while trying to open an imported synapse configuration >>>>>>>> - [TOOLS-2027 <https://wso2.org/jira/browse/TOOLS-2027>] - CApp >>>>>>>> POM editor does not save property changes >>>>>>>> - [TOOLS-2039 <https://wso2.org/jira/browse/TOOLS-2039>] - >>>>>>>> Cloud connector operation parameters doesn't get displayed in >>>>>>>> properties >>>>>>>> view properly >>>>>>>> - [TOOLS-2082 <https://wso2.org/jira/browse/TOOLS-2082>] - ESB >>>>>>>> project is created inside GReg project >>>>>>>> - [TOOLS-2083 <https://wso2.org/jira/browse/TOOLS-2083>] - >>>>>>>> Resources Editor window can not be opened once closed >>>>>>>> - [TOOLS-2084 <https://wso2.org/jira/browse/TOOLS-2084>] - >>>>>>>> Duplicate resource files do not trigger error >>>>>>>> - [TOOLS-2088 <https://wso2.org/jira/browse/TOOLS-2088>] - [Dev >>>>>>>> Studio]When you create custom folders inside synapse config, Dev >>>>>>>> Studio >>>>>>>> will give errors while importing it in to Dev Studio. >>>>>>>> - [TOOLS-2089 <https://wso2.org/jira/browse/TOOLS-2089>] - >>>>>>>> Resource Key Editor dialog displays incorrect workspace Registry >>>>>>>> keys >>>>>>>> - [TOOLS-2092 <https://wso2.org/jira/browse/TOOLS-2092>] - >>>>>>>> Error while deserializing HTTP endpoint >>>>>>>> - [TOOLS-2093 <https://wso2.org/jira/browse/TOOLS-2093>] - DevS >>>>>>>> removes the target sequence from the Iterate mediator >>>>>>>> - [TOOLS-2094 <https://wso2.org/jira/browse/TOOLS-2094>] - >>>>>>>> Remove Create New Synapse Config option in wizard since new editor >>>>>>>> does not >>>>>>>> support >>>>>>>> - [TOOLS-2103 <https://wso2.org/jira/browse/TOOLS-2103>] - AF >>>>>>>> perspective should close if user cancel the login window >>>>>>>> - [TOOLS-2108 <https://wso2.org/jira/browse/TOOLS-2108>] - Save >>>>>>>> credential option does not functioning properly >>>>>>>> - [TOOLS-2110 <https://wso2.org/jira/browse/TOOLS-2110>] - >>>>>>>> Null-Pointer Exception while open proxy-services >>>>>>>> >>>>>>>> Task >>>>>>>> >>>>>>>> - [TOOLS-2081 <https://wso2.org/jira/browse/TOOLS-2081>] - >>>>>>>> Rename Carbon Applications to Composite Applications >>>>>>>> >>>>>>>> Sub-task >>>>>>>> >>>>>>>> - [TOOLS-1227 <https://wso2.org/jira/browse/TOOLS-1227>] - Can >>>>>>>> not configure target related configs via UI in iterate mediator and >>>>>>>> dose >>>>>>>> not serialize the target attributes. >>>>>>>> - [TOOLS-1715 <https://wso2.org/jira/browse/TOOLS-1715>] - >>>>>>>> Support for HTTP Endpoint >>>>>>>> - [TOOLS-1891 <https://wso2.org/jira/browse/TOOLS-1891>] - >>>>>>>> require statement >>>>>>>> - [TOOLS-2069 <https://wso2.org/jira/browse/TOOLS-2069>] - list >>>>>>>> of statement when press ctrl + space >>>>>>>> - [TOOLS-2070 <https://wso2.org/jira/browse/TOOLS-2070>] - list >>>>>>>> down the jaggery Built-ins variables >>>>>>>> - [TOOLS-2071 <https://wso2.org/jira/browse/TOOLS-2071>] - >>>>>>>> Syntax Coloring to special keywords >>>>>>>> - [TOOLS-2077 <https://wso2.org/jira/browse/TOOLS-2077>] - list >>>>>>>> down the Built-ins methods >>>>>>>> - [TOOLS-2079 <https://wso2.org/jira/browse/TOOLS-2079>] - Code >>>>>>>> assistance Doc for Built-ins variables >>>>>>>> - [TOOLS-2080 <https://wso2.org/jira/browse/TOOLS-2080>] - Code >>>>>>>> Assistance doc for built-ins methods >>>>>>>> >>>>>>>> Wish >>>>>>>> >>>>>>>> - [TOOLS-1916 <https://wso2.org/jira/browse/TOOLS-1916>] - Out >>>>>>>> of the box IntelliJ support >>>>>>>> >>>>>>>> Your feedbacks are most welcome. Please report issues at [3] and >>>>>>>> specify the affect version as 3.3.0 Alpha 3. >>>>>>>> >>>>>>>> [1] >>>>>>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/Alpha3/wso2-developer-studio_3.3.0.zip >>>>>>>> [2] >>>>>>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/Alpha3/installed-distributions/ >>>>>>>> [3] https://wso2.org/jira/browse/TOOLS >>>>>>>> >>>>>>>> >>>>>>>> Thanks and Regards, >>>>>>>> WSO2 Developer Studio Team. >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Asanka Sanjeewa* >>>>>>>> Senior Software Engineer >>>>>>>> Mobile: +94772532924 >>>>>>>> WSO2 Inc. http://wso2.com/ >>>>>>>> Blog: http://asanka-tech-blog.blogspot.com/ >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Harshana Martin >>>>>> Associate Technical Lead >>>>>> WSO2 Inc. : http://wso2.com >>>>>> >>>>>> Mobile: +94 775 998 115 >>>>>> Profile: https://www.google.com/profiles/harshana05 >>>>>> Blog: http://harshana05.blogspot.com >>>>>> Twitter: http://twitter.com/harshana05 >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Harshana Martin >>>> Associate Technical Lead >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 775 998 115 >>>> Profile: https://www.google.com/profiles/harshana05 >>>> Blog: http://harshana05.blogspot.com >>>> Twitter: http://twitter.com/harshana05 >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Chintana Wilamuna >>> Architect - Solution Architecture >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> phone: +94 72 145 4545 >>> blog: http://engwar.com/ >>> photos: http://flickr.com/photos/chintana >>> linkedin: http://www.linkedin.com/in/engwar >>> twitter: twitter.com/std_err >>> >> >> >> >> -- >> >> Harshana Martin >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 775 998 115 >> Profile: https://www.google.com/profiles/harshana05 >> Blog: http://harshana05.blogspot.com >> Twitter: http://twitter.com/harshana05 >> >> >> _______________________________________________ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Viraj Rajaguru > Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile: +94 77 3683068 > > > > > _______________________________________________ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
