[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orekit Developers] New tasking
Hank Grabowski <hank@applieddefense.com> a écrit :
I finally got the unit tests running inside my Eclipse so I could run the
code profiler. I'm going to take a look at which functions to start
banging away at more based on that. My methodology was going to be to
augment tests that were already stimulating the framework in cases where
that is appropriate and only create explicitly new tests when that would be
infeasible. I do not intend to change any of the existing assertions, these
would all be additions to a test, no changes or subtractions.
Once I have tests modified, how should I submit them for review and
inclusion?
You could create a patch with respect to the latest Git version. From
a console, the command line would be "git diff -p > orekit.patch".
From Eclipse, you can also create a patch using the context menu in
the explorer pane "Team -> Create patch..." and follow the wizard.
Once the patch is created, attach it to a new ticket in our issue tracker.
best regards,
Luc
On Fri, Nov 15, 2013 at 4:53 PM, Hank Grabowski
<hank@applieddefense.com>wrote:
Sounds good, I'll get started on some of the unit test stuff and move on
from there. Should I just open up tracker incidents as I do them so I can
commit through attachments again?
--
Hank Grabowski
Chief Technology Officer
10440 Little Patuxent Parkway, Suite 600
Columbia, MD 21044
(410) 715-0005 Office
(410) 715-0008 Fax
(301) 525-6219 Mobile
hank@applieddefense.com
www.AppliedDefense.com <http://www.applieddefense.com/>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.