You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/02/18 21:43:12 UTC

[jira] [Commented] (MESOS-2372) Test suite for verifying compatibility between Mesos components

    [ https://issues.apache.org/jira/browse/MESOS-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326523#comment-14326523 ] 

Niklas Quarfot Nielsen commented on MESOS-2372:
-----------------------------------------------

Great idea. How have you guys been doing this so far?

It will probably be a big undertaking to host it in the mesos source itself. How about starting an effort under github.com/mesos with that kind of integration testing? It'll probably involve pull down prebuilt older versions of Mesos and run an integration test suite, like we discussed during our last community meeting.

> Test suite for verifying compatibility between Mesos components
> ---------------------------------------------------------------
>
>                 Key: MESOS-2372
>                 URL: https://issues.apache.org/jira/browse/MESOS-2372
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>
> While our current unit/integration test suite catches functional bugs, it doesn't catch compatibility bugs (e.g, MESOS-2371). This is really crucial to provide operators the ability to do seamless upgrades on live clusters.
> We should have a test suite / framework (ideally running on CI vetting each review on RB) that tests upgrade paths between master, slave, scheduler and executor.



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