Path: csiph.com!news.swapon.de!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Eclipse question
Date: Fri, 27 Oct 2017 10:45:45 -0400
Organization: Aioe.org NNTP Server
Lines: 24
Message-ID: <osvgqo$1usm$1@gioia.aioe.org>
References: <051ea305-3fc8-4087-bd2a-bd4c7bd131c5@googlegroups.com> <14pdv8gcyixc2$.nrjypzl7wkp7.dlg@40tude.net> <a539e9c2-d3cf-4bf9-8a77-c78605ec1b3b@googlegroups.com>
NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
X-Notice: Filtered by postfilter v. 0.8.2
Content-Language: en-US
Xref: csiph.com comp.lang.java.programmer:37591

On 10/27/2017 9:41 AM, Eric Douglas wrote:
>                       This is not a JUnit test, I'm not trying
> to execute every line of code in my API.  I don't even know much
> about JUnit, haven't written a test, am just developing an API where
> I have been the primary or sole developer.

Maybe time to learn something new?

:-)

>                                     I don't even know how one
> would write an automated test of a full API that would tell you
> things like "what does this custom JTable run through when I click
> this cell".

UI code is not as easy to unit test as other layers.

But just unit testing the underlying layers is still good.

And there are some tools for unit testing UI's as well.

Arne