Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
Hi Harshana, On Thu, Nov 21, 2013 at 2:37 PM, Harshana Martin harsh...@wso2.com wrote: Hi Samisa, On Thu, Nov 21, 2013 at 2:31 PM, Samisa Abeysinghe sam...@wso2.comwrote: Given there is no auto test help, to guard against slips, lets at least use a checklist of all mediators to be tested. Yes.. That's a good idea.. we did such cross check when we did DevS 3.0.0 release. So we will reuse the same set to make sure no slip ups. 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. 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. When can we get CAR files to cover all mediators? we can add some base tests to cover deploy, undeploy and re-deployment of CAR files and allow ESB team to complete the rest. Thanks, Krishantha. 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.comwrote: Hi Samisa, On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe sam...@wso2.comwrote: 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.comwrote: 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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
Given there is no auto test help, to guard against slips, lets at least use a checklist of all mediators to be tested. 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. 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.comwrote: 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.comwrote: 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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
Hi Samisa, On Thu, Nov 21, 2013 at 2:31 PM, Samisa Abeysinghe sam...@wso2.com wrote: Given there is no auto test help, to guard against slips, lets at least use a checklist of all mediators to be tested. Yes.. That's a good idea.. we did such cross check when we did DevS 3.0.0 release. So we will reuse the same set to make sure no slip ups. 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. 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.comwrote: Hi Samisa, On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe sam...@wso2.comwrote: 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.comwrote: 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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
Some of the bugs I've encountered are mainly UI related bugs. Just out of curiosity, is there facilities in Eclipse framework to automate those? Like for example, configuration disappears when switching to source view after designing the mediation flow in ESB graphical editor. -Chintana On Thu, Nov 21, 2013 at 2:37 PM, Harshana Martin harsh...@wso2.com wrote: Hi Samisa, On Thu, Nov 21, 2013 at 2:31 PM, Samisa Abeysinghe sam...@wso2.comwrote: Given there is no auto test help, to guard against slips, lets at least use a checklist of all mediators to be tested. Yes.. That's a good idea.. we did such cross check when we did DevS 3.0.0 release. So we will reuse the same set to make sure no slip ups. 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. 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.comwrote: Hi Samisa, On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe sam...@wso2.comwrote: 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.comwrote: 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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
Hi Chintana, Yes. There is. We've started using SWTBot, an Eclipse UI Testing framework for this task. With that we can test these thing. The downside is, the programming model for SWTBot is quite tedious. We have to tell exact step by step to follow which takes time but in the same time provide us the great flexibility. So we can definitely do it. On a separate note, when it comes to DevS 3.3.0, we have fixed majority of such incidents. There are couple of such scenarios which we are trying to fix at the moment. Thanks and Regards, Harshana On Thu, Nov 21, 2013 at 3:02 PM, Chintana Wilamuna chint...@wso2.comwrote: Some of the bugs I've encountered are mainly UI related bugs. Just out of curiosity, is there facilities in Eclipse framework to automate those? Like for example, configuration disappears when switching to source view after designing the mediation flow in ESB graphical editor. -Chintana On Thu, Nov 21, 2013 at 2:37 PM, Harshana Martin harsh...@wso2.comwrote: Hi Samisa, On Thu, Nov 21, 2013 at 2:31 PM, Samisa Abeysinghe sam...@wso2.comwrote: Given there is no auto test help, to guard against slips, lets at least use a checklist of all mediators to be tested. Yes.. That's a good idea.. we did such cross check when we did DevS 3.0.0 release. So we will reuse the same set to make sure no slip ups. 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. 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.comwrote: Hi Samisa, On Thu, Nov 21, 2013 at 6:50 AM, Samisa Abeysinghe sam...@wso2.comwrote: 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.comwrote: 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
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
What is the plan to test all mediators for basic functionality for 3.3.0? I understand that some mediators were badly broken in 3.2.0 release e.g. XACML. 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. 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
[Dev] Developer Studio 3.3.0 Alpha 3 Released!
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
