lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laimonas Simutis (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LUCENENET-419) Tests should be categorized
Date Thu, 24 Jan 2019 22:25:00 GMT

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

Laimonas Simutis closed LUCENENET-419.
--------------------------------------
    Resolution: Incomplete

This seems like an outdated ticket that has not had response.

> 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.0.3, Lucene.Net 4.8.0
>         Environment: All
>            Reporter: michael herndon
>            Assignee: michael herndon
>            Priority: Major
>              Labels: test, testing
>   Original Estimate: 40h
>  Remaining Estimate: 40h
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message