[jira] [Closed] (LUCENENET-632) Review tests for Lucene.Net assembly

["Shad Storhaug (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENENET-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shad Storhaug closed LUCENENET-632.
-----------------------------------
    Resolution: Abandoned

Moved to GitHub: https://github.com/apache/lucenenet/issues/259

> Review tests for Lucene.Net assembly
> ------------------------------------
>
>                 Key: LUCENENET-632
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-632
>             Project: Lucene.Net
>          Issue Type: Improvement
>          Components: Lucene.Net Test
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Priority: Minor
>              Labels: up-for-grabs
>   Original Estimate: 40h
>  Remaining Estimate: 40h
>
> A line-by-line review would be best, but at the very least we should be checking that the implementations are complete and the test conditions are the same as in [Java Lucene 4.8.0|https://github.com/apache/lucene-solr/tree/releases/lucene-solr/4.8.0]. Checking at the method level to ensure they all exist and have the right attributes has been completed already on Lucene.Net (core).
> Occasionally, tests are still being found with important lines that have been commented because the functionality didn't exist at the time they were ported. We need some assurance that none of our green tests are false positives.
> The tests that are most likely to have issues are the tests for
> # Lucene.Net (core)
> # Lucene.Net.Classification
> # Lucene.Net.Codecs
> # Lucene.Net.Expressions
> # Lucene.Net.Facet
> # Lucene.Net.Join
> # Lucene.Net.Queries



--
This message was sent by Atlassian Jira
(v8.20.1#820001)