[
https://issues.apache.org/jira/browse/MESOS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198515#comment-14198515
]
Till Toenshoff commented on MESOS-1894:
---------------------------------------
Added an additional step that now does typed testing within the mesos test
suite. That way the CRAMMD5Authentication tests are run against both, the
default (built-in) CRAMMD5Authenticator as well as against the modularized
version of that class.
https://reviews.apache.org/r/27619/
> 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)
