You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Irindu Nugawela <nb...@gmail.com> on 2018/05/04 12:45:42 UTC
Writing Tests For an Output Connector
Hi devs,
I was examining the tests written for output connectors ElasticSearch and
CMIS. I noticed the test classes for CMIS were
APISanityHSQLDBIT
BaseITHSQLDB
BaseHSQLDB
BasePostgresql
BaseUIHSQLDB
NavigationHSQLDBUI
in addition to these Elastic Search had two more test classes
SanityHSQLDBTest
SanityPostgresqlTest
Please help me understand the naming convention of these connectors and
which of these fall under unit tests and what are the classes falling under
integration tests.
I am supposed to write unit tests for the MongoDB Output Connector, what
are the general guidelines for writing unit tests? is there a reference for
writing tests? which of the above-mentioned test classes are relevant for
MongoDB connector. Please help me with my questions. Thanks in advance.
--
Thanks and Regards,
Irindu Nugawela,
Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate,
Faculty of Engineering University of Peradeniya
Re: Writing Tests For an Output Connector
Posted by Irindu Nugawela <nb...@gmail.com>.
Thank you very much, Karl, and Thank you very much Piergiorgio.
On 4 May 2018 at 19:12, Piergiorgio Lucidi <pi...@apache.org> wrote:
> Just finished a videocall with Irindu about this.
>
> Thank you Karl for your reply.
>
> Cheers,
> PJ
>
> 2018-05-04 14:55 GMT+02:00 Karl Wright <da...@gmail.com>:
>
>> Hi Irindu,
>>
>> (1) The base classes for the tests begin with "Base".
>> (2) Integration tests include "IT" at the end
>> (3) The database that is used comes right before the "IT", and there are
>> several you could write, e.g.: HSQLDB, PostgreSQL, Mysql.
>>
>> When you use the ant run-IT-HSQLDB, for instance, it runs all tests named
>> xxxHSQLDBIT.
>>
>> For the connector projects you are working on, you probably need just
>> HSQLDB tests. This is because you're really not exercising any
>> database-specific functionality.
>>
>> Karl
>>
>>
>> On Fri, May 4, 2018 at 8:45 AM Irindu Nugawela <nb...@gmail.com>
>> wrote:
>>
>> > Hi devs,
>> >
>> > I was examining the tests written for output connectors ElasticSearch
>> and
>> > CMIS. I noticed the test classes for CMIS were
>> >
>> > APISanityHSQLDBIT
>> > BaseITHSQLDB
>> > BaseHSQLDB
>> > BasePostgresql
>> > BaseUIHSQLDB
>> > NavigationHSQLDBUI
>> >
>> > in addition to these Elastic Search had two more test classes
>> >
>> > SanityHSQLDBTest
>> > SanityPostgresqlTest
>> >
>> > Please help me understand the naming convention of these connectors and
>> > which of these fall under unit tests and what are the classes falling
>> under
>> > integration tests.
>> >
>> > I am supposed to write unit tests for the MongoDB Output Connector, what
>> > are the general guidelines for writing unit tests? is there a reference
>> for
>> > writing tests? which of the above-mentioned test classes are relevant
>> for
>> > MongoDB connector. Please help me with my questions. Thanks in advance.
>> >
>> >
>> > --
>> > Thanks and Regards,
>> > Irindu Nugawela,
>> > Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate,
>> > Faculty of Engineering University of Peradeniya
>> >
>>
>
>
>
> --
> Piergiorgio Lucidi
> https://www.open4dev.com
>
--
Thanks and Regards,
Irindu Nugawela,
Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate,
Faculty of Engineering University of Peradeniya
Re: Writing Tests For an Output Connector
Posted by Piergiorgio Lucidi <pi...@apache.org>.
Just finished a videocall with Irindu about this.
Thank you Karl for your reply.
Cheers,
PJ
2018-05-04 14:55 GMT+02:00 Karl Wright <da...@gmail.com>:
> Hi Irindu,
>
> (1) The base classes for the tests begin with "Base".
> (2) Integration tests include "IT" at the end
> (3) The database that is used comes right before the "IT", and there are
> several you could write, e.g.: HSQLDB, PostgreSQL, Mysql.
>
> When you use the ant run-IT-HSQLDB, for instance, it runs all tests named
> xxxHSQLDBIT.
>
> For the connector projects you are working on, you probably need just
> HSQLDB tests. This is because you're really not exercising any
> database-specific functionality.
>
> Karl
>
>
> On Fri, May 4, 2018 at 8:45 AM Irindu Nugawela <nb...@gmail.com>
> wrote:
>
> > Hi devs,
> >
> > I was examining the tests written for output connectors ElasticSearch and
> > CMIS. I noticed the test classes for CMIS were
> >
> > APISanityHSQLDBIT
> > BaseITHSQLDB
> > BaseHSQLDB
> > BasePostgresql
> > BaseUIHSQLDB
> > NavigationHSQLDBUI
> >
> > in addition to these Elastic Search had two more test classes
> >
> > SanityHSQLDBTest
> > SanityPostgresqlTest
> >
> > Please help me understand the naming convention of these connectors and
> > which of these fall under unit tests and what are the classes falling
> under
> > integration tests.
> >
> > I am supposed to write unit tests for the MongoDB Output Connector, what
> > are the general guidelines for writing unit tests? is there a reference
> for
> > writing tests? which of the above-mentioned test classes are relevant for
> > MongoDB connector. Please help me with my questions. Thanks in advance.
> >
> >
> > --
> > Thanks and Regards,
> > Irindu Nugawela,
> > Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate,
> > Faculty of Engineering University of Peradeniya
> >
>
--
Piergiorgio Lucidi
https://www.open4dev.com
Re: Writing Tests For an Output Connector
Posted by Karl Wright <da...@gmail.com>.
Hi Irindu,
(1) The base classes for the tests begin with "Base".
(2) Integration tests include "IT" at the end
(3) The database that is used comes right before the "IT", and there are
several you could write, e.g.: HSQLDB, PostgreSQL, Mysql.
When you use the ant run-IT-HSQLDB, for instance, it runs all tests named
xxxHSQLDBIT.
For the connector projects you are working on, you probably need just
HSQLDB tests. This is because you're really not exercising any
database-specific functionality.
Karl
On Fri, May 4, 2018 at 8:45 AM Irindu Nugawela <nb...@gmail.com> wrote:
> Hi devs,
>
> I was examining the tests written for output connectors ElasticSearch and
> CMIS. I noticed the test classes for CMIS were
>
> APISanityHSQLDBIT
> BaseITHSQLDB
> BaseHSQLDB
> BasePostgresql
> BaseUIHSQLDB
> NavigationHSQLDBUI
>
> in addition to these Elastic Search had two more test classes
>
> SanityHSQLDBTest
> SanityPostgresqlTest
>
> Please help me understand the naming convention of these connectors and
> which of these fall under unit tests and what are the classes falling under
> integration tests.
>
> I am supposed to write unit tests for the MongoDB Output Connector, what
> are the general guidelines for writing unit tests? is there a reference for
> writing tests? which of the above-mentioned test classes are relevant for
> MongoDB connector. Please help me with my questions. Thanks in advance.
>
>
> --
> Thanks and Regards,
> Irindu Nugawela,
> Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate,
> Faculty of Engineering University of Peradeniya
>