[ https://issues.apache.org/jira/browse/MESOS-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler reassigned MESOS-8511: -------------------------------------- Assignee: Benjamin Mahler > Provide a v0/v1 test scheduler to simplify the tests. > ----------------------------------------------------- > > Key: MESOS-8511 > URL: https://issues.apache.org/jira/browse/MESOS-8511 > Project: Mesos > Issue Type: Improvement > Components: test > Reporter: Benjamin Mahler > Assignee: Benjamin Mahler > Priority: Major > Labels: tech-debt > > Currently, there are a lot of tests that just want to launch a task in order > to test some behavior of the system. These tests have to create their own v0 > or v1 scheduler and invoke the necessary calls on it and expect the necessary > calls / messages back. This is rather verbose. > It would be helpful to have some better abstractions here, like a > TestScheduler that can launch tasks and exposes the status updates for them, > along with other interesting information. E.g. > {code} > class TestScheduler > { > // Add the task to the queue of tasks that need to be launched. > // Returns the stream of status updates for this task. > Queue<StatusUpdate> addTask(const TaskInfo& t); > etc > } > {code} > Probably this could be implemented against both v0 and v1, if we want to > parameterize the tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)