You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2014/11/05 16:31:33 UTC

[jira] [Updated] (MESOS-1894) Authenticator Module: Tests

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

Till Toenshoff updated MESOS-1894:
----------------------------------
    Sprint: Mesosphere Q4 Sprint 2 - 11/14

> Authenticator Module: Tests
> ---------------------------
>
>                 Key: MESOS-1894
>                 URL: https://issues.apache.org/jira/browse/MESOS-1894
>             Project: Mesos
>          Issue Type: Improvement
>          Components: modules
>            Reporter: Till Toenshoff
>            Assignee: Till Toenshoff
>            Priority: Blocker
>
> h4. Motivation
> Make sure that an authenticator module can be fully unit- and integration- tested within the mesos test suite.
> h4. Status Quo
> We currently have a few CRAM-MD5 specific authentication integration tests ( {{tests/sasl_tests.cpp}} ) as well as a complete authentication test list for authentication as a whole with some CRAM-MD5 specifics again ( {{tests/authentication.cpp}} ). 
> h4. Approach
> 1. MESOS-1864 needs to get fleshed out, providing a module integration test scheme for our mesos test suite
> 2. refactor / move / rename integration tests of the CRAM-MD5 specific tests {{tests/sasl_tests.cpp}} & {{tests/authentication.cpp}}
> 3. implement tests via a parameterized version of {{tests/authentication.cpp}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)