‎2007 Jun 05 2:54 PM
how do you do the Unit testing?....and what is the transaction code for TESTING?
‎2007 Jun 05 2:57 PM
hi,
after creating report,
just press F8.it will give u output.......
based on your selection parameter u can test ur report...........
if u want debug than set break point.........
reward points if helpful,
Regards,
Imran
‎2007 Jun 05 2:58 PM
Hi,
Unit testing is nothing but debug testing ...
Unit testing is done with your stand alone development say a class or a program developed by you and is done by a person from testing team. In this you will check for negative logic (something like what will happen if you dont enter correct values to the input parameters), labels and also for getting output with maximum possible inputs. Normally there are guidelines available for this with testing team. It is mostly a generic guideline for all the platforms say SAP or JAVA... So the starting point of this testing is your development. The most important things to be checked are the texts in your error or warning or information messages, labels printed in the screens and or header, footers. Also verify the output format is matching with what is mentioned in the functional spec by the object owner from client side.
ABAP Unit Testing can, if done very carefully and extensively, almost completely replace debugging which is a synonym for unsystematic testing.
Unit Tests bridge the gap between low-level testing and high-level testing of entire processes using eCATT.
If you have a class with several methods of a function group with several function modules you can define for each method and function module one or many Unit Tests. Using these Unit Tests you can demonstrate that your methods and function modules work according to you expectations. Even more important, when you change your coding you can use your Unit Tests to check whether you accidentially introduced some error.
Another very interesting way of programming is test-driven development (TDD). This basically means that you create a test first based on the specification which, of course, will fail in the beginning because there isn't any application. Now you develop until the Unit Test will be passed.
Reward if useful.
Thanks
Aneesh.
‎2007 Jun 05 3:00 PM
Hi,
Use the T-Code SCAT or SECATT
Also a lot of utilities are a part of the testing package
SQL Tace : ST05
T-Code : STWB_WORK -> Testing performance
Also these is Code analyser
Code Inspector
Runtime Monitor & EPC
‎2007 Jun 05 3:11 PM