Hi Pat, Yes, unit tests. The Scala code we write in an engine, especially DataSource & Algorithm, can get quite complicated. Driving development with a fast unit-testing suite is a boon for creating engines & collaborating on them, especially for those of us who are not Scala experts.
I've got ScalaTest unit tests working in the skeleton template for everything but the DataSource, where I hit a JDBC connection pool error: https://github.com/apache/incubator-predictionio-template-skeleton/pull/5#issuecomment-285818113 *Mars ( <> .. <> ) > On Mar 9, 2017, at 13:29, Pat Ferrel <[email protected]> wrote: > > Unit tests? I tend to test it with integration tests since that finds more > problems than simple unit tests. There is a new Python integration test > framework but I’m still using bash scripts > > > On Mar 9, 2017, at 11:30 AM, Mars Hall <[email protected]> wrote: > > Have any of you ever written tests for DataSource? > > Any recommendations on how to handling seeding test data into the event > storage or wrapping test runs in transactions to clean any changes between > each test? > > context: > https://github.com/apache/incubator-predictionio-template-skeleton/pull/5 > > *Mars Hall > Customer Facing Architect > Salesforce App Cloud / Heroku > San Francisco, California > >
