About unit test plan document

Hi all,
I am new to ABAP environment.Can anyone explain what is meant by unit test plan document and also what is the diff between between code review and peer review.
Thanks in advance
*There is enough material online, pl help yourself.
@Others: Answering such questions is discouraged.*
Edited by: Suresh Datti on Sep 1, 2009 10:35 AM

Hi,
Unit test plan:
From a technical point of view , once you complete your development you need to test the objet to ensure it is meeting all the requirements..
For this purpose you prepare a unit test plan. You will have both negative and positive test case in your plan. Execute each case and check whether the output is acheived or not..
Code review.. Once coding is completed you need to review your code to ensure that you have followed all coding stds..
Peer review is code review done by; some one else in your team.
Search SCN for more details
Regards
Ansari

Similar Messages

How to write utp(unit test plan)

how to write utp(unit test plan)

Hi,
Steps to be followed for UTP.
UTP : Unit Test Plan. Testing the program by the developer who developed the program is termed as Unit Test Plan.
Two aspects are to be considered in UTP.
1. Black Box Testing
2. White Box Testing.
1. Black Box Testing : The program is executed to view the output.
2. White Box Testing : The code is checked for performance tuning and syntax errors.
Follow below mentioned steps.
Black Box Testing
1. Cover all the test scenarios in the test plan. Test plan is usually prepared at the time of Techincal Spec preparation, by the testing team. Make sure that all the scenarios mentioned in the test plan are coverd in UTP.
2. Execute your code for positive and negative test. Postive tests - to execute the code and check if the program works as per expected. Negative Test - Execute code to know if the code is working in scenarios in which it is not supposed to work. The code should work only in the mentioned scenarios and not in all cases.
White Box Testing.
1. Check the Select statments in your code. Check if any redundant fields are being fetched by the select statements.
2. Check If there is any redundant code in the program.
3. Check whether the code adheres to the Coding standards of your client or your company.
4. Check if all the variables are cleared appropriately.
5. Optimize the code by following the performance tuning procedures.
Using tools provided by SAP
1. Check your program using EXTENDED PROGRAM CHECK.
2. Use SQL Trace to estimate the performace and the response of the each statement in the code. If changes are required, mention the same in UTP.
3. Use Runtime Analyser and Code Inspector to test your code.
4. Paste the screen shots of all the tests in the UTP document. This gives a clear picture of the tests conducted on the program.
All the above steps are to be mentioned in UTP.
Regards,
Vara

Test Plan Document Template

Hi Team,
Does anybody have a test plan document i could use as a template for an ETl dataflow and related processing in external systems.
Thank You

Hi,
Unit test plan:
From a technical point of view , once you complete your development you need to test the objet to ensure it is meeting all the requirements..
For this purpose you prepare a unit test plan. You will have both negative and positive test case in your plan. Execute each case and check whether the output is acheived or not..
Code review.. Once coding is completed you need to review your code to ensure that you have followed all coding stds..
Peer review is code review done by; some one else in your team.
Search SCN for more details
Regards
Ansari

Required Unit test Plan for Data migration

Dear All,
I am looking for unit test plan Draft documents/templates which covers
1. Testing tools
2. Methods
3. Error handling
4. Reviews and approvals
The project is a Oracle 10g data migration from one schema to another schema.
It will be a greate help if anyone can forward the same to me.
Thank you.

Hi Vaishali,
You may wish to refer the links below...
https://service.sap.com/instguides --> SAP NetWeaver --> Release 2004s --> Upgrade
https://www.sdn.sap.com/irj/sdn/developerareas/bi
latest on upgrade tp BI7.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
Upgrading BW 3.X to SAP NetWeaver 2004s BI (PDF 2.6 MB)
Front End Migration strategy
Here's the migration strategy: Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
Presentation
http://csc-studentweb.lrc.edu/swp/Berg/Articles/PM_2006_upgrade_NW2004s_Bjarne_Berg_v12.ppt
Here are the frontend requirements:
Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
Here are the backend requirements in the product availabilty matrix:
https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200615320900001250
Migration of Web Teplates
832713 - Migration of Web templates from BW 3.x to Netweaver
Assign points if this helps.
Regards,
Anil

Need Sample Unit Test Plan templates for SD

Hi Experts,
I am in need of some SD unit test plan templates used in any of your implementations.
Pls Help.

Dear Preethi
As already expressed, you are asking the confidential document which nobody would like to share.
However, AS-IS will be prepared by Core team people and your duty is to go through the process in depth.
May be the AS-IS from SD purview, I can list as an example as how it should be
The excel sheet of AS-IS header tabs will have to contain the following header tabs
- Scenario like Exports, Domestic etc,
- Under this scenario, Groups like OE, Aftermarket, Stock Transfer etc.,
- Under this Groups, Process like Business Plan, Scheduling, Preshipment activities, Post shipment activities etc.,
- Finally this process has to be break down into a detailed list of activities.
So you have to go through these process in detail.
As for as testing is concerned, there is no need to check the customer master.
All you have to do is to carry out all standard T.Codes like order creation, create delivery, PGI, Billing and Excise Invoice. Again try to cancel all documents from billing to sale order and ensure that you are able to cancel those documents. Check for the FI implication on the COGS and material cost.
Also while testing, you can also check whether you are able to create one delivery against multiple sale orders and one invoice against multiple deliveries. If not successful, analyse the reason for split, maintain the required datas in masters and retry the process.
thanks
G. Lakshmipathi

Unit test plan for inbound and outbound interfaces

I am trying to create a UNIT TEST PLAN for an interface. In this interface a flat file in IDOC format is picked up from the application server and processed using EDI_DATA_INCOMING for the relevant posting ( example : Sales order creation from a PO IDOC). IF the file is not in IDOC format then it is reformatted to the IDOC format manually.
In second scenario(outbound), after sales order creation or billing document creation, IDOC is created which is read and a custom flat file is created and sent to a middleware.
PLease suggest a unit test plan for these kind of scenarios or send a sample UTP if possible.
REgards
Nishant
PS: points will be awarded to helpful answers.

Unfortunately this isn't possible, the esa has only one routing table. You'll have to add specific routes for your internal networks.
I usually avoid two-armed setups because of this and it gets even worse if you want to use virtual gateways (traffic gets sent via the internal interface with an IP from the external interface)

Abt unit test plan

hi
can u plz explain abt unit test planning?
es

hi bramara,
Unit testing is used to test the proper working of a single module.
Integration testing is used to test the integration between the modules,
when the complete business scenario of a client is tested (say from sales order creation to receipt of money from customer).
Unit Testing
When you test every single document is called unit testing.
String Testing
One transaction full activity is called string testing. For example Vendor
invoice, goods received and vendor payment.
Integration Testing
It is purely with other modules and we have to check whether the FI testing
is working with other related modules or not.
Testing of combined parts of an application to determine if they function
together correctly.There are three types of integration testing.1. Big bang
testing: Testing with all modules combined together invariable of its
levels. Often done for small projects.2. Bottom up test:Testing by
integrating lower level modules and ascending towards the higher-level
modules.3. Top down: Testing the higher-level modules and descending towards
the lower level modules.This can be accomplished with dummy modules to
replace the under construction modules with so-called stubs and drivers.
not.
Regression Testing
Testing for whole database. Bring all the data into another server and do
the testing is called regression.
Thanks,
<REMOVED BY MODERATOR>
kushagra
Edited by: Alvaro Tejada Galindo on Jan 31, 2008 9:45 AM

What is UTP?(unit test plan)

hi,
what is UTP?
How do you write UTP?(unit test plan)

Hi,
Are u referring to the UTP which is to be done after u hve completed the coding. If so, UTP is a document where in u write the test cases and the test results of the object that you have developed. It will have the test case, expected result and the result that is displyed in the output. You can also provide the screenshots of the output and also comments in the document.
Hope this helps.
Reward points if helpful.
Thanks.

How to prepare the UNIT test plan

Hi ALL
can any body tell me how to prepare a unit test plan

Use the following colums in preparing unit Test data.
1. Sr.No.
2.Test Condition.
3.Expected Results
4.Description/Instruction for the test execution.
5.TestData used for the test.
6.Actual Result.
7.Pass/Fail.
For a login Screen. Unit Test plan wud b.
1. 1
2. User Presses Login Button.
3. Data shud be validated.
4. As soon as the user enter the fields in the login screen,the data shud be validated and If entered data is correct proceed to the next screen, else popup an error.
5. User:kiran, Pwd:***
6. Entered incorrect data,but proceeded to the new screen.
7. FAIL.

How can we do unit test plan

hi experts can u help me plz

Hi,
Check this
http://www.softwareqatest.com/qatfaq2.html#FAQ2_6b
You find a description about Test Plan.

How to send a mail about the test plan status

Hi
I have finished the development of ecatt automation test cases.
And I have integrated the ecatt automation test cases into the test plan of TWB.
I have scheduled a job in background to run the test plan.
After the job has finished, I need to send a email to related users to tell them the status of each test cases in the test plan.
Is there any way to implement it?
Thanks a lot in advance!

Hello,
You can send mail with the status of the test catalog-
specify a mail system to which Test Workbench test objects send messages to the people responsible
Please refer the below link for more information:
http://help.sap.com/saphelp_smehp1/helpdata/en/6a/88370a002911d2bd02080009b4534c/frameset.htm
Regards,

How to edit test case document?

Hello All, 
 
In SOLAR02 transaction, we are uploading the test case documents in the test cases tab. 
 
Later we can create test plans & test packages. These test packages once assigned to the tester, it comes in the worklist of the tester. 
 
The tester while testing the test cases, can record the test results from the test workbench using the traffic light symbolled icon. 
 
But, my requirement is to edit the test case document and to give some explanation about what all went right and what all went wrong. 
Is that possible? 
 
Any inputs in this regard will be greatly appreciated. 
 
Thanks & Best regds, 
Alagammai 

Hi all,
I was looking for the similar info on the net, and I run into this, saying:
Here is some info from sdn.com
This depends on your support package level. But at least in one of the latest support packages this was made possible. You need to make a little customizing in transaction STWB_SET. Under "Notes" you must mark "Use test document". This means that in STWB_WORK when you add a note for a specific test case then a copy is made of your test script in which you can then enter results. This is then done without editing the test script template document.
If this customizing is not available then you have to apply the latest solman 7.0 support packages.
Thanks, just what was needed!!
Now test plan documents can be opened in STWB_WORK and edited there. Remark is that in creating the test plan (STWB_2), Test note drop down list should have the same value as the test document in Test cases tab (SOLAR02).
Would it be possible also to open test documents (Word, Excel, etc) in STWB_WORK in full screen somehow? That was not yet managed to be done.
Me personally haven't tried it yet, as I have to finish some other jobs first, but I thought it would be nice to share the info
Regards,
N

EDQ Test planning and recording

Hi,
I'm working on a data deduplication and matching project using EDQ. We need to document our unit test plans and evidence. EDQ allows easy manual checking of dataflows but I don't want to waste time taking screen grabs and producing unwieldy documents. Are there any test planning or test automation tools that we can use? Failing that is it possible to export the results and evidence that each function has worked? If neither of these are options can i ask how others capture unit test evidence?
Thanks
Jason

Actually, we are running Analyzer and Essbase on the same server and reports on a seperate server. I inherited the Essbase/Analyzer configuration and since it is working well, I'm not looking to mess with it. Reports worked out well because we had just decommissioned a server that was running SpiderMan (Hyperion Enterprise Web tool) when we took Spiderman down, it freed up a perfectly good server which was already configured for Internet access. The install of reports was smoother than we could have hoped for.oh, and we do not have planning..Still using Pillar.

UAT and TEST Case Document

Hi,
For Exchange 2013, do we have microsoft technet link for User acceptance Test and Test Plan document post implementation/migration.
Thanks
jitender

Hi,
Based on my search, there is no official document about User Acceptance Test and Test cases for Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Need to write international Unit Test.

Hello All. I�d like to write a 16-bit charset unit test and view the results in eclipse. Can anyone tell me how to do so?
I�m writing an application that needs to support international characters. The app will someday support Japanese, Hindi, Hebrew, Chinese, etc. No one in the office has written code in these languages.
I�d like to write a JUnit test to ensure that my persistence layer can save �Hello World� in one of these languages and retrieve the exact String. I found a site showing me how to write Hello World in Japanese http://unix.org.ua/orelly/java-ent/servlet/ch12_03.htm, but System.out.println("\u4eca\u65e5\u306f\u4e16\u754c"); displays �?????�. I�d like to be able to preview the unit test from Eclipse and run it from ANT. What do I need to do to accomplish this?
Thanks in advance,
Steven

Hi,
Steps to be followed for UTP.
UTP : Unit Test Plan. Testing the program by the developer who developed the program is termed as Unit Test Plan.
Two aspects are to be considered in UTP.
1. Black Box Testing
2. White Box Testing.
1. Black Box Testing : The program is executed to view the output.
2. White Box Testing : The code is checked for performance tuning and syntax errors.
Follow below mentioned steps.
Black Box Testing
1. Cover all the test scenarios in the test plan. Test plan is usually prepared at the time of Techincal Spec preparation, by the testing team. Make sure that all the scenarios mentioned in the test plan are coverd in UTP.
2. Execute your code for positive and negative test. Postive tests - to execute the code and check if the program works as per expected. Negative Test - Execute code to know if the code is working in scenarios in which it is not supposed to work. The code should work only in the mentioned scenarios and not in all cases.
White Box Testing.
1. Check the Select statments in your code. Check if any redundant fields are being fetched by the select statements.
2. Check If there is any redundant code in the program.
3. Check whether the code adheres to the Coding standards of your client or your company.
4. Check if all the variables are cleared appropriately.
5. Optimize the code by following the performance tuning procedures.
Using tools provided by SAP
1. Check your program using EXTENDED PROGRAM CHECK.
2. Use SQL Trace to estimate the performace and the response of the each statement in the code. If changes are required, mention the same in UTP.
3. Use Runtime Analyser and Code Inspector to test your code.
4. Paste the screen shots of all the tests in the UTP document. This gives a clear picture of the tests conducted on the program.
All the above steps are to be mentioned in UTP.
Regards,
Vara

About unit test plan document

Similar Messages

Maybe you are looking for