You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/05/17 00:02:16 UTC

[jira] [Updated] (MESOS-1060) Provide a means of mocking out process exits for testing.

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

Benjamin Mahler updated MESOS-1060:
-----------------------------------

    Fix Version/s:     (was: 0.19.0)

> Provide a means of mocking out process exits for testing.
> ---------------------------------------------------------
>
>                 Key: MESOS-1060
>                 URL: https://issues.apache.org/jira/browse/MESOS-1060
>             Project: Mesos
>          Issue Type: Improvement
>          Components: test
>            Reporter: Benjamin Mahler
>
> There are many places in the code where we perform a process exit in order to commit suicide in the Master and the Slave. We'd like to be able to test these code paths without exiting the testing binary.
> This is a common situation and google-test provides a 'Death Test' testing abstraction to deal with this. However, this works by forking which may be problematic with libprocess:
> https://code.google.com/p/googletest/wiki/AdvancedGuide#Death_Tests
> https://code.google.com/p/googletest/wiki/AdvancedGuide#How_It_Works
> https://code.google.com/p/googletest/wiki/AdvancedGuide#Death_Tests_And_Threads



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