On Thu, Sep 18, 2014 at 10:34 PM, Chanaka Jayasena chan...@wso2.com wrote:
Normally firebug console will give an error for missing resources. For the
console.log statements developers should scan manually find out them and
remove them before releasing the component.
exactly that is how I
Is there any possibility to find these type of issues though UI testing?
In addition to the missing resources, there are console.log statements also.
On Wed, Sep 17, 2014 at 7:00 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
+1 for having checking procedure.
I have notice same issue in
Normally firebug console will give an error for missing resources. For the
console.log statements developers should scan manually find out them and
remove them before releasing the component.
thanks,
Chanaka
On Fri, Sep 19, 2014 at 2:42 AM, Udara Rathnayake uda...@wso2.com wrote:
Is there any
Hi,
Since we ship webapps with most of the products(AM,ES,UES etc..) now, its
better if we can test and resolve missing resources while releasing
products. All the time we don't have a method to track valid dependencies
and also reluctant to remove current dependencies since we are not sure
about
+1 for having checking procedure.
I have notice same issue in several packs.
IMO we can add this validation part on QA process.
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Thu, Sep 18, 2014 at 12:12 AM, Udara Rathnayake uda...@wso2.com wrote:
