You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/02/07 23:16:35 UTC

[jira] [Updated] (SPARK-4746) integration tests should be separated from faster unit tests

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

Sean Owen updated SPARK-4746:
-----------------------------
    Component/s: Tests

> integration tests should be separated from faster unit tests
> ------------------------------------------------------------
>
>                 Key: SPARK-4746
>                 URL: https://issues.apache.org/jira/browse/SPARK-4746
>             Project: Spark
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Imran Rashid
>            Priority: Trivial
>
> Currently there isn't a good way for a developer to skip the longer integration tests.  This can slow down local development.  See http://apache-spark-developers-list.1001551.n3.nabble.com/Spurious-test-failures-testing-best-practices-td9560.html
> One option is to use scalatest's notion of test tags to tag all integration tests, so they could easily be skipped



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org