You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Ignatenko (JIRA)" <ji...@apache.org> on 2018/08/18 18:12:00 UTC
[jira] [Commented] (IGNITE-9316) Analyse and improve code coverage
in ML module (follow-up to IGNITE-9146)
[ https://issues.apache.org/jira/browse/IGNITE-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584862#comment-16584862 ]
Oleg Ignatenko commented on IGNITE-9316:
----------------------------------------
improved tests are in branch https://github.com/gridgain/apache-ignite/tree/ignite_9316
> Analyse and improve code coverage in ML module (follow-up to IGNITE-9146)
> -------------------------------------------------------------------------
>
> Key: IGNITE-9316
> URL: https://issues.apache.org/jira/browse/IGNITE-9316
> Project: Ignite
> Issue Type: Task
> Components: ml
> Affects Versions: 2.6
> Reporter: Oleg Ignatenko
> Assignee: Oleg Ignatenko
> Priority: Major
> Labels: unit-test
> Fix For: 2.7
>
>
> Studying of coverage reports attached in IGNITE-9146 suggests that many default methods in interfaces are not covered by tests.
> In particular the default methods in the following interfaces look like worth covering in tests:
> {noformat}
> org.apache.ignite.ml.Model
> org.apache.ignite.ml.math.functions.IgniteTriFunction
> org.apache.ignite.ml.dataset.PartitionDataBuilder
> org.apache.ignite.ml.dataset.PartitionContextBuilder
> org.apache.ignite.ml.dataset.Dataset
> org.apache.ignite.ml.environment.parallelism.Promise
> org.apache.ignite.ml.composition.predictionsaggregator.PredictionsAggregator{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)