‎2006 Oct 19 8:48 AM
‎2006 Oct 19 8:50 AM
hi,
u can debugg ur program.
either set break point or after execution type /h.
SE30 - gives you a run time analysis and points out the issues more at design time.
ST05 - Is the most useful if you want to track time taken for execution of each of the sections.
SM50 - Will give you a work process overview, not sure at a program level how can it help you.
Some times you will have to use a combination of SE30 and ST05.
I would like to use St05 personally.
rgds
anver
if hlpful pls mark points
‎2006 Oct 19 6:21 PM
Check this SAP help link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/10/6d1c370c468b7be10000009b38f936/frameset.htm
I guess this will defintely help you
Enjoy SAP
Pankaj
‎2006 Oct 19 6:44 PM
hi,
yes .. of course..
you can debug abap programs.. set breakpoints at certain portion of the code to analyse the same.
you can define different test scenerios for programs..
‎2006 Oct 27 5:14 PM
hi,
is your query answered? if yes, please close the thread and award points for helpful answers.
‎2006 Nov 02 9:55 AM
Hi,
You can do testing on abap very well using breakpoints and watchpoints also check the following links too.
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/87273c3f2b3c7ce10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/87273c3f2b3c7ce10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/97/87273c3f2b3c7ce10000000a11402f/content.htm
Also if you to do dynamic or run time testing just provide the inputs and write "/h "
the status bar shows debugging switched on now when you press execute of f8 the command goes inside and now you can check for the values of individual variables or internal table contents etc.
Also check the foll links,
http://www.sap-basis-abap.com/sapab002.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/07/88273c3f2b3c7ce10000000a11402f/content.htm
Please reward for the same.
‎2006 Nov 02 2:48 PM
Hi,
Thru debug it is possible.
Use field,table tabs to find out data is populating corrcetly or not in debug window.
put break points & watch points where it is required.
Thanks
Sunil
‎2006 Nov 03 9:35 AM
hi,
u can debugg ur program.
either set break point or after execution type /h.
SE30 - gives you a run time analysis and points out the issues more at design time.
ST05 - Is the most useful if you want to track time taken for execution of each of the sections bsed on SQL trace most of the time...in ur program.
AL21 give the Anlysis of ur Program..
STAT : Give the Statstics of ur porgram and also...better fucntionality..
Kindly reward points...
regards
manish
‎2006 Nov 05 7:52 PM
Hello Sekhar
Three of the most important testing procedures have not been mentioned yet:
(1) <b>ABAP Unit Testing</b> (requires >= 6.40)
(2) <b>Checkpoint Groups</b> (requires >= 6.20)
(3) <b>eCATT</b> (testing of entire functions / processes)
ABAP Unit Tests allow you to define within your program objects tests to ensure that your forms/methods work correctly.
Checkpoint Groups allow you to explicitly define assertions in the coding about states in the application.
For documentation see the Weblog series by Thomas Weiss about <a href="/people/thomas.weiss/blog/2004/12/17/a-spotlight-on-abap-unit-part-1 Unit Tests</a>
and <a href="/people/claudia.dangers/blog/2005/09/07/how-to-instrument-your-abap-code-with-checkpoint-groups Groups</a>.
Regards
Uwe