Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0D021200D18 for ; Wed, 27 Sep 2017 00:53:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0B6171609EA; Tue, 26 Sep 2017 22:53:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 507061609D7 for ; Wed, 27 Sep 2017 00:53:03 +0200 (CEST) Received: (qmail 22839 invoked by uid 500); 26 Sep 2017 22:53:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 22828 invoked by uid 99); 26 Sep 2017 22:53:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 22:53:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D39AC1A2BB4 for ; Tue, 26 Sep 2017 22:53:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id l-YWB-79Q-C7 for ; Tue, 26 Sep 2017 22:53:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E24D761116 for ; Tue, 26 Sep 2017 22:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 75391E0E4F for ; Tue, 26 Sep 2017 22:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2CDA024266 for ; Tue, 26 Sep 2017 22:53:00 +0000 (UTC) Date: Tue, 26 Sep 2017 22:53:00 +0000 (UTC) From: "Eric Yang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-7202) End-to-end UT for api-server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 26 Sep 2017 22:53:04 -0000 [ https://issues.apache.org/jira/browse/YARN-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181706#comment-16181706 ] Eric Yang edited comment on YARN-7202 at 9/26/17 10:52 PM: ----------------------------------------------------------- [~jianhe] The test case are designed to be unit tests for ApiServer without over reaching. It also covers the input validation in ServiceClient. It is possible to write additional tests to focus on ServiceClient correctness which can increase test coverage. However, I think it is easy to mistaken unit test verse integration test. Without good coverage at interface level, integration test may not help to identify the root problems. I can't say I am familiar with ServiceClient code to write unit tests for it. I can write unit tests for new code that I am about to add to ServiceClient for storing Service spec. However, it would be helpful for original author who wrote ServiceClient to add test code. was (Author: eyang): [~jianhe] The test case are designed to be unit tests for ApiServer without over reaching. It also covers the input validation in ServiceClient. It is possible to write additional tests to focus on ServiceClient correctness which can increase test coverage. However, I think it is easy to mistaken unit test verse integration test. Without good coverage at interface level, integration test may not help to identify the root problems. I can't say I am familiar with ServiceClient code to write unit tests for it. I can write unit tests for new code that I am about to add to ServiceClient for storing Service config. However, it would be helpful for original author who wrote ServiceClient to add test code. > End-to-end UT for api-server > ---------------------------- > > Key: YARN-7202 > URL: https://issues.apache.org/jira/browse/YARN-7202 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Jian He > Attachments: YARN-7202.yarn-native-services.001.patch, YARN-7202.yarn-native-services.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org