What is the best recommendations for automated tests of applications that use Ignite? On one hand you have Unit test purists that insist that you should be mocking data that is coming from Ignite. On the other hand, you have more practical people that say if you do that, you can't actually unit test your code that uses Ignite.
If it matters, we're using Ignite.Net fat client and NUnit as our unit testing framework. I have verified that a standalone ignite works in a unit test. But I imagine we need to ensure things like: * prevent concurrently running unit tests from forming a cluster * ensure each unit test has its own work directory and this is cleared out before running each test. -- Kathryn Hogg Principal Technology Architect
