Tests should be categorized
----------------------------
Key: LUCENENET-419
URL: https://issues.apache.org/jira/browse/LUCENENET-419
Project: Lucene.Net
Issue Type: Task
Components: Build Automation, Lucene.Net Test
Affects Versions: Lucene.Net 3.x
Environment: All
Reporter: michael herndon
Assignee: michael herndon
We should break down the tests into categories.
Possible Categories:
* ones that ensure the test env is set up correctly for any integration tests.
* integration tests
* unit tests (ones that use RAMDirectory, in memory objects, etc)
* any others that may be useful.
The unit tests should always run. The integration tests should fail when things
are not set up right.
CI should run these by categories.
The testing env should help anyone looking to verify their testing setup. e.g.
The test require a temp directory as an Environment Variable. It would be
helpful to put things like these into their own tests to verify the setup and
help developers figure out what they are missing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
