You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2016/01/08 22:07:39 UTC
[jira] [Created] (MESOS-4317) Document use of mesos specific future
design patterns in gmock test framework
Avinash Sridharan created MESOS-4317:
----------------------------------------
Summary: Document use of mesos specific future design patterns in gmock test framework
Key: MESOS-4317
URL: https://issues.apache.org/jira/browse/MESOS-4317
Project: Mesos
Issue Type: Documentation
Reporter: Avinash Sridharan
Priority: Minor
Mesos relies heavily on google test and google mock frameworks for its unit test infrastructure. In order to support unit testing of mesos classes that are inherently designed to be multi-threaded (or multi-process), and asynchronous in nature, the libprocess future/promise design patterns have been used to expose a set of API that allow for asynchronous callbacks within the mesos specific gmock test framework (3rdparty/libprocess/include/process/gmock.hpp) .
Given that these future/promise based API is very specific to the apache mesos test framework it would be good to have documentation to better inform developers (especially newbies) of the infrastructure and its use-cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)