[LUCENENET-419] Tests should be categorized

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: Lucene.Net 3.0.3, Lucene.Net 4.8.0
• Component/s: Build Automation, Lucene.Net Test
• Labels: test testing

Environment

All

• Assignee: michael herndon
• Reporter: michael herndon
• Created: 27/May/11 18:13
• Updated: 24/Jan/19 22:24
• Resolved: 24/Jan/19 22:24

Description

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.