Hi Senaka, Currently we don't currently have have something of this nature. This will be a good addition to integration level tests ,ie we do package level operations in integration tests.
Thank you, Dharshana. On Sun, Oct 21, 2012 at 10:24 PM, Senaka Fernando <[email protected]> wrote: > Hi Krishantha, Dharshana, > > Do we have $subject or equivalent. Ideally this class should have multiple > test methods. > > 1. Validation of jar files against LICENSE.txt > 2. Checking whether jar duplication has happened. > 3. Recursive scan for no occurrence of SNAPSHOT in file names and contents > of textual files (.txt, .xml, etc). > 4. Checking whether Maven variables are properly replaced inside > configuration files found inside repository/conf > 5. Product specific checks for whether samples/resources are properly > packaged. The file list should not have versions. The test should fail if > there are files that are not on the file list, or if files on the file list > are missing. Failures should mention a summary of what needs to be fixed. > > Please do let me know so that I can create corresponding issues. > > Thanks, > Senaka. > > -- > *Senaka Fernando* > Member - Integration Technologies Management Committee; > Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > -- Dharshana Warusavitharana Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : [email protected] <[email protected]> cell : +94772202595 blog : http://dharshanaw.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
