Hi Dimuthu, The correct approach to validate any xml is using a XSD. its generic. So you can use XSD instead of one to one mapping of an xml. Since we have a limited number of config files we can come up with an XSD which validates key configuration parts.
And it won't be a generic or a good approach to use one to one mapping on all configs. I think XSD approach is also easy to implement. Thank You, Dharshana. On Wed, Oct 23, 2013 at 5:28 AM, Dimuthu De Lanerolle <[email protected]>wrote: > Hi Krishantha, > > 1 & 2 - Ok. We will start modifying the test cases accordingly. > > 4. Our approach to tackle this scenario is to maintain some product > specific configuration files (carbon.xml etc.) inside the Automation > Framework which will contain entries which needs to be checked and perform > a one-to-one check with the corresponding configuration file/s inside the > product distribution. Also note that configuration files inside the TAF > only contains xml tags, which are getting updated at the build time > together with some additional tags to provide essential information the > test case might need. > > > On Tue, Oct 22, 2013 at 5:56 PM, Krishantha Samaraweera < > [email protected]> wrote: > >> Hi Dimuthu, >> >> On Thu, Oct 17, 2013 at 5:46 PM, Dimuthu De Lanerolle >> <[email protected]>wrote: >> >>> We are in the process of writing test cases to validate the contents >>> inside a product distribution. Mentioned below is the progress as at today. >>> >>> 1. Validation of jar files inside plugins directory against LICENSE.txt >>> - Completed. >>> >> >> Validation should be done inside other directories such as >> repository/lib, components/dropins etc..Also you need to check whether any >> jars are missing in LICENSE.txt file. >> >> >>> 2. Recursive scan for no occurrence of SNAPSHOT in file names and >>> contents of textual files (.txt, .xml, etc) - Completed. >>> >> >> Please extend the tests case to verify SNAPSHOT in file names. And we >> might need to disable this test case in trunk. >> >> >>> >>> 3. Validate duplication entries in LICENSE file. - Completed. >>> >> 4. Checking whether Maven variables are properly replaced inside >>> configuration files found inside repository/conf - In progress >>> >> >> Can you elaborate on the validation approach you are going to follow for >> different type of configuration files in products. >> >> Thanks, >> Krishantha. >> >> >>> >>> Regards >>> >>> -- >>> Dimuthu De Lanerolle >>> Software Engineer >>> WSO2 Inc. >>> lean . enterprise . middlewear. >>> http://wso2.com/ >>> Tel. : +94 11 2145345 Fax : +94 11 2145300 email : [email protected] >>> >>> >>> _______________________________________________ >>> 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. >> > > > > -- > Dimuthu De Lanerolle > Software Engineer > WSO2 Inc. > lean . enterprise . middlewear. > http://wso2.com/ > Tel. : +94 11 2145345 Fax : +94 11 2145300 email : [email protected] > > > _______________________________________________ > 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
