Unit Tests Failures

[TonyAbell]

80: Failed
22: Pass

Are all the unit tests up to date and in working order.

I am planning on refactoring the project to make it easier to plug in different storage and index providers.

Should I make sure the tests are up to date, or are they not being maintained.

[brianpos]

I didn't think it was that bad.

need to have the mongo store initialized with the correct test data before running the tests.

I would be happy to join in with the development work.

we would like to put a SQL server store behind it, and also make it more easily “grafted” onto existing systems.

Brian

From: Tony Abell
Sent: ‎Monday‎, ‎15‎ ‎September‎ ‎2014 ‎9‎:‎45‎ ‎AM
To: furore-fhir/spark

80: Failed
22: Pass

Are all the unit tests up to date and in working order.

I am planning on refactoring the project to make it easier to plug in different storage and index providers.

Should I make sure the tests are up to date, or are they not being maintained.

—
Reply to this email directly or view it on GitHub.

[TonyAbell]

@brianpos are you at the HL7 meeting this week?

I have started the process here #18

[ewoutkramer]

Hi Tony,

We are using these tests ourselves as well for integration tests of Spark, so they should run. But we were a bit behind when arriving in Chicago. Did you manage to get more success during the connectathon?

[mharthoorn]

I am planning on refactoring the project to make it easier to plug in different storage and index provider
We have separated the modules and will publish them as NUGET packages.

[mharthoorn]

We are in the process of readding a new set of unit tests. The previous project is out of date. Also, our primary tool for testing is Sprinkler (http://github.com/furore-fhir/sprinkler)