Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Question re testing constructor Date: Tue, 06 Dec 2011 16:40:24 -0800 Organization: Canadian Mind Products Lines: 23 Message-ID: References: Reply-To: Roedy Green NNTP-Posting-Host: Z2l1DcCELS0rATq8NqV4Sw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10576 On Tue, 6 Dec 2011 15:14:18 +0000 (UTC), Novice wrote, quoted or indirectly quoted someone who said : > >It seems to me - correct me if I'm wrong - that I can easily test to make >sure the constructor actually built SOMETHING by testing the object against >null. The idea is to test YOUR code not Sun/Oracle's . Constructors never produce null and never produce objects of the wrong type. Factories might, but not constructors. What you might want is an assert that makes sure you remembered to init all necessary fields in the object. -- Roedy Green Canadian Mind Products http://mindprod.com For me, the appeal of computer programming is that even though I am quite a klutz, I can still produce something, in a sense perfect, because the computer gives me as many chances as I please to get it right.