Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Eclipse question Date: Fri, 27 Oct 2017 19:05:43 -0400 Organization: Aioe.org NNTP Server Lines: 21 Message-ID: References: <051ea305-3fc8-4087-bd2a-bd4c7bd131c5@googlegroups.com> <14pdv8gcyixc2$.nrjypzl7wkp7.dlg@40tude.net> <2120adec-27d9-4a73-ba65-501806e891f5@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: 8bit 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 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:37600 On 10/27/2017 2:23 PM, Eric Douglas wrote: > On Friday, October 27, 2017 at 2:08:26 PM UTC-4, Arne Vajhøj wrote: >> It is a huge task to write really complete tests. >> >> But my take on that is that non-complete tests are better than no >> tests. > > Input-output is easy enough when my input is 2 and 6, my method is > mutiply() and my result is 12. > How do you write a complete test when my input is end user, my > method is "drag mouse from GUI control A to control B", and my > result is "does the end model show what the user expects". Some just test the underlying logic and not the UI. Some use special UI test frameworks to automate user actions. Arne