× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Hi Sam,

Is it possible to create a small testcase to reproduce the problem? Can you
please open a PMR and attach the testcase to the report.

Thanks,
____________________________________________________________________________
Maha Masri
Rational Developer for i - Rational Developer for AIX and Linux - Rational
Developer for Power




From: Sam Hansen <Sam.Hansen@xxxxxxxxxxxxxx>
To: "wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>
Date: 04/27/2016 04:47 PM
Subject: Re: [WDSCI-L] Expectations of Code Cover Results
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Thanks Edward,

I only use a static SEP when I'm doing an ad-hoc test. When running full
scripts, I create Code Coverage Configurations. The application for
analysis is listed in the "What to Analyze" section, the calling
application is in the "How to Start" command, and I have the configuration
set to launch in background in the Common tab. I start the coverage
analysis using the drop down icon on the toolbar for code coverage and then
the name of the configuration.

Sam

Are you using SEP to start code coverage? If yes, do you set the SEP on
the runner program or the test case? If you set an SEP on the test case,
the SEP location >might have an impact on whether code coverage is invoked
for a test. If the SEP is set on the test program, code coverage should be
invoked for every test case >run. However, if the SEP is set on a procedure
inside the test case, then code coverage is only invoked when the procedure
is called in a particular test run.

Also make sure that when you set the SEP on the runner application, you go
into the 'Open Launch Configuration' dialog (right click on SEP in the IBM
i Service >Entry Points view) and add it to the programs to be analyzed
list.

This email message and any attached files contain information intended
solely for the use of the individual(s) or entity to which it is addressed
and may contain information that is proprietary, privileged and/or
confidential. If you are not an intended recipient, please (i) notify the
sender, (ii) do not review, forward, copy or distribute this email or any
attached files, and (iii) delete the original message.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.