You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/08/22 17:12:10 UTC

[jira] [Resolved] (AURORA-645) Improve coverage of clientv2 commands

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

Mark Chu-Carroll resolved AURORA-645.
-------------------------------------

    Resolution: Fixed

> Improve coverage of clientv2 commands
> -------------------------------------
>
>                 Key: AURORA-645
>                 URL: https://issues.apache.org/jira/browse/AURORA-645
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Mark Chu-Carroll
>            Assignee: Mark Chu-Carroll
>
> The current suite of unit tests for clientv2 commands is focused on testing API behavior: it runs client commands, and verify that the commands perform the correct interactions with a mocked scheduler.
> These tests do not currently test the command outputs. At the time they were implemented, the command implementations were preliminary, and we anticipated that we'd be likely to make frequent changes to the formatting of command output, and so implementing tests was delayed until things stabilized.
> Clientv1 commands are now generating deprecation messages, and clientv2 is stable. The output from commands shouldn't be changing frequently, so it's a good time to look at adding coverage of outputs.
> In addition, in the last week, we've had a scattering of bug reports related to exactly this - places where output is hard to read, or where the formatting isn't optimal, or where something is missing.
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)