Hi Kasper, I understood your point around integration tests, but my query was more regarding the developer's perspective. Suppose I am working on enhancement/bug under any data source connector say (SQLServer), I am expected to test the changes locally before raising the PR. This would require a setup of my own. Tomorrow I might be working on any other data source, which would require its own setup to verify the changes. Does dev/contributor follow this approach and set up a data source locally to verify the functionality? It might not be possible to set up every data source locally sometimes, so how does dev proceed in those cases?
Thanks & Regards Ratish Bansal On Fri, Apr 24, 2020 at 3:20 AM Kasper Sørensen < i.am.kasper.soren...@gmail.com> wrote: > Hi Ratish, > > Testing against all the databases is not required. We offer those tests as > occasional integration tests that we run whenever we consider the changes > to be related to that database. The integration tests themselves typically > contain javadoc that explains what the prerequisites are. > > The main technical documentation is located in our wiki ( > https://cwiki.apache.org/confluence/display/METAMODEL). I would suggest > you > read through the "Key concepts" pages listed out on the front page. > > Best regards, > Kasper > > Den tor. 16. apr. 2020 kl. 13.43 skrev RATISH BANSAL <ratish1...@gmail.com > >: > > > Hello All, > > > > I was looking to start contributing to Metamodel, so I analyzed and > picked > > a few JIRA ticket for beginners to start with. However, I am facing some > > difficulties mentioned below. > > > > 1. How do we test the changes? As per my understanding, we do need an > > actual respective data source setup to verify. Does each contributor > > setup > > a data source locally? Is there another way, since it won't be > feasible > > to > > setup so many data sources? > > 2. Do we have any technical documentation to understand the current > > architecture, so as to assist new contributors? > > > > It would be great if someone could help. > > > > Thanks & Regards > > Ratish Bansal > > >
