Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3844218C19 for ; Mon, 4 Jan 2016 05:07:45 +0000 (UTC) Received: (qmail 32130 invoked by uid 500); 4 Jan 2016 05:07:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 32042 invoked by uid 500); 4 Jan 2016 05:07:40 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 32020 invoked by uid 99); 4 Jan 2016 05:07:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 05:07:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CAF9A2C1F56 for ; Mon, 4 Jan 2016 05:07:39 +0000 (UTC) Date: Mon, 4 Jan 2016 05:07:39 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-13721: ----------------------------------- Fix Version/s: (was: 2.3.0) 2.4.0 > Ambari functional tests infrastructure > -------------------------------------- > > Key: AMBARI-13721 > URL: https://issues.apache.org/jira/browse/AMBARI-13721 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.2.0 > Reporter: Nahappan Somasundaram > Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > > Run a test version of the ambari-server with an in-memory DB and ambari-agent that run during the functional testing and cover several basic use cases like heartbeat monitoring, adding and deleting services, components, hosts, etc. > * Functional test design: > * The functional tests run the same way as unit tests, using JUnit > * Enabling/disabling of the functional tests can be done using a Maven configuration. > * The building blocks of the functional tests are: > ** A local ambari server that wraps the actual AmbariServer implementation with Guice to instantiate an in-memory database (use the existing InMemoryDefaultTestModule class) > ** Methods to set up a default cluster with a few hosts, with each host running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods use the ambari server's RESTful APIs. > ** Methods that use HttpClient to perform operations using the RESTful APIs to add/remove cluster, hosts, services, service components and service component hosts. > ** A simple functional test to start the local server on a thread, get status from the server and then shutdown. > * Additional unit tests can be built on top of the start-status check-stop functional tests, default cluster setup method and helper methods to test specific scenarios. > > *Future work: > * Local ambari agent simulator for each host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)