[
https://issues.apache.org/jira/browse/ARIA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856159#comment-15856159
]
ASF GitHub Bot commented on ARIA-99:
------------------------------------
Github user ran-z commented on a diff in the pull request:
https://github.com/apache/incubator-ariatosca/pull/67#discussion_r99840764
--- Diff: tests/resources/service_templates/node-cellar/types/aria.yaml ---
@@ -0,0 +1,93 @@
+
+policy_types:
--- End diff --
lol I understand, but the problem is this yaml import should be part of the
extension code and not part of the tests. I realize it's not there right now
but I think you might as well have thrown it over there instead right now, no?
Unless I'm missing something, and you think this duplication will remain
even once we do have it as part of the extension..?
> Straightforward end-to-end tests for parser and built-in workflow
> -----------------------------------------------------------------
>
> Key: ARIA-99
> URL: https://issues.apache.org/jira/browse/ARIA-99
> Project: AriaTosca
> Issue Type: Task
> Reporter: Tal Liron
> Assignee: Tal Liron
> Priority: Minor
>
> The idea is to start with a comprehensive blueprint and end up with valid
> results. Essentially all mechanisms in ARIA will be tested except for the
> actual CLI package -- the tests will simulate what happens when a user enters
> a CLI command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
