Hi Suzie, I'm sorry that I'm nowhere near understanding the Java part of this, but I will see if I can find something that will help you. I know that Eclipse has documentation about this. Jim From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - Kansas City, MO Sent: Friday, July 22, 2011 3:57 PM To: program-java@xxxxxxxxxxxxx Subject: [program-java] Re: running JUNIT tests Covered refers to the number of lines tested. For example, it you tested a getter you might test six lines. I'm not getting the exception listed as I thought I would even with alt shift q. I want to do it at work on Monday. This is my telework day and I don't have anyone who can help me. I need someone who actually understands what I am doing. I get the test run and now I know if it failed. That's something. Susie From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James Sent: Friday, July 22, 2011 2:01 PM To: program-java@xxxxxxxxxxxxx Subject: [program-java] Re: running JUNIT tests Hi Suzie, What does covered refer to? Jim From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - Kansas City, MO Sent: Friday, July 22, 2011 2:41 PM To: program-java@xxxxxxxxxxxxx Subject: [program-java] Re: running JUNIT tests I'm working with this. At least that is pointing me in the right direction. Aren't any of the rest of you having to run JUNIT tests? I went to a class on Maven yesterday and doing this was covered a little bit in the class. All this seems so much deaper than what I was doing with simply compiling and running my own stuff. There is a report of all these tests which comes out when changes are made. Among other things it tells management how many lines of code have been covered. They want something like 80%. The percentage can really rise quickly if you write these ascert statements for getters and setters. Then you ask the question "What good is all this?" Susie Thanks. From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James Sent: Friday, July 22, 2011 1:15 PM To: program-java@xxxxxxxxxxxxx Subject: [program-java] Re: running JUNIT tests Hi Suzie, I hope this works. Try Alt+Shift+Q, then type the letter x. I think you would then type Enter after that, but I'm unsure. Jim From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - Kansas City, MO Sent: Friday, July 22, 2011 1:51 PM To: program-java@xxxxxxxxxxxxx Subject: [program-java] Re: running JUNIT tests I need to find out if a test failed or succeeded. Susie From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Corbett, James Sent: Friday, July 22, 2011 12:49 PM To: 'program-java@xxxxxxxxxxxxx' Subject: [program-java] Re: running JUNIT tests Suzy: Ok, what are you asking? Jim ________________________________ From: program-java-bounce@xxxxxxxxxxxxx [mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Stanzel, Susan - Kansas City, MO Sent: July 22, 2011 12:49 To: program-java@xxxxxxxxxxxxx Subject: [program-java] running JUNIT tests Hi Listers, Here at U.S.D.A. and other places, to make sure something has not suddenly broken JUNIT tests are run. You have the ascert, a message, what you expect and the actual result. I am trying to know if a test passes or not. Naturally this is where a little red x shows or a green plus sign. I am trying to get to the results of this test in some kind of meaningful fashion. To run a JUNIT test you have the method, like a get, highlighted and then you hit the applications key which they call right clicking and arrow down to run as JUNIT. I hope some of this makes more sense to you than it is to me. Susie Stanzel ________________________________ This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.