Hi all, We have around 170 test-cases in the registry kernel, covering various aspects, and individual test-cases would actually test a significant portion of functionality. However, these were always tested against a single registry.xml. But, there are many things that can be configured via the registry.xml (ex:- caching, registry root, auto-versioning etc), which would cause the execution-paths to change. Therefore, until recently, some execution paths were never tested. I have recently introduced multiple registry.xml files against which these tests would run, ensuring that all execution paths are covered. This has increased the effective number of tests to over 1250.
Due to this, you will notice that it takes sometime to compile the registry kernel with tests. But, this delay (though painful), ensures that the code that we run will not break for a user. I just wanted to give a quick heads up so that you'd be aware of what's going on. And, I am still to figure out how to start a remote H2 server while running the registry kernel tests, and once that's done, I'll be adding configurations that would cover multiple mounting scenarios. This would further increase the number. But, before I do that, I'll figure out how a profile can be introduced to avoid running all of these tests, but the generic subset. Thanks, Senaka. -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate 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://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
