[ http://issues.apache.org/jira/browse/SOLR-3?page=comments#action_12370218
]
Hoss Man commented on SOLR-3:
-----------------------------
>There are probably some opportunities to use Java5 stuff like varargs...
> doc("id",42,"subject","easy")
...i'm doing that in validateAddDoc (which calls makeSimpleDoc) ... are there
other methods you think it also makes sense for?
> Also what we really need is a way to dynamically add/create a schema, so one
> could add
> a new analysis filter,
> then define a fieldtype & field that uses it and test it out, without
> modifying some global
> testing schema.
i was operating under the assumption that for stuff like that, the best thing
to do would be to have multiple sets of solrconfig/schema files ... for Solr
itself there would probably be one big generic file that most tests could use,
but any test that wanted to try something exotic would check in a new one (in a
directory with the same name as the test class) and speciy it when constructing
hte harness.
the only flaw in that plan right now is that SolrCore only lets you specify a
schema file path when you construct it, not a solrconfig, but i was going to
tackle refactoring that once i had the basics up and running.
> create test harness and port TestApp to junit
> ---------------------------------------------
>
> Key: SOLR-3
> URL: http://issues.apache.org/jira/browse/SOLR-3
> Project: Solr
> Type: Task
> Reporter: Hoss Man
> Priority: Minor
> Attachments: TestBasicFunctionality.java, TestHarness.java
>
> To both encourage good internal development, and to make it easy for plugin
> developers to write unit tests of their own code I think we need a harness
> that makes it easy to unit test updates and queries against Solr (without
> needing a servlet container)
> Once we have this, i think we can/should also retire "TestApp" in favor of
> some JUnit tests (which would probably make more sense for other developers)
> Iv'e already started on this, i thought i'd have something to commit tonight,
> but i got distracted ... filing this bug as a tracker for now.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
