[
https://issues.apache.org/jira/browse/FALCON-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230288#comment-14230288
]
Venkatesh Seetharam commented on FALCON-919:
--------------------------------------------
This is a step in the right direction but can we actually make these tests
correspond to a particular *resource* in the source code and model these tests?
entity/submit
entity/schedule
....
or feed/schedule
....
lifecycle/replication
lifecycle/eviction
lifecycle/latedata
....
metadata/lineage
metadata/discovery
....
instances/list
instances/pagination
instances/summary
> Test classes reorganization
> ---------------------------
>
> Key: FALCON-919
> URL: https://issues.apache.org/jira/browse/FALCON-919
> Project: Falcon
> Issue Type: Sub-task
> Components: merlin
> Affects Versions: 0.6
> Reporter: Paul Isaychuk
> Assignee: Paul Isaychuk
> Fix For: 0.7
>
> Attachments: falcon-919.diff
>
>
> *The idea is to split up all tests between matching packages*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
