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

Similar Messages

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 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

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)

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.

ABAP UNIT TEST

Hi ,
I am new to oops concept but i am able to understand.
Now i have to create some Unit test plans in ABAP.We are using SAP Netwever 7.1 and WEB AS 6.0
I tried from SE24 but i couldn't get the correct path.
Can you please explain me: if i have a Z program then where and how to write number of Unit test classes. And how it will integrate to with our actual program/FM/any object
Thanks
Umashankar.

You can create the ABAP Unit class as a local class in your program, FM, or class which will test the functionality of that individual code lines. Once you implement the ABAP Unit, you can then run the Unit Test by main menu > Execute > Unit Test. E.g. from Program, Program > Execute > Unit Test.
Check this previous discussions:
ABAP Unit, how to use
Unit Testing concept
Regards,
Naimesh Patel

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

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.

Unit test and program

Hi all,
I created Ztable and i created table maintenance generator and Tcode for Ztable .
Now my query is I want to create program for ztable to test the data.
plz provide me the program and unit test plan for ztable.its urgent.

Hi,
Please check if this helps.
    MODIFY s076 FROM TABLE i_final2.
    IF sy-subrc = 0.
      MESSAGE s900 WITH text-007."Data inserted into table S076
    ENDIF.
ELSE.
    MESSAGE s900 WITH text-012."Data not inserted into table S076
ENDIF.
You can display such messages in your program output screen after the datas are inserted into the ztable.
regards,
Priya.

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

Unit Testing, Null, and Warnings

I have a Unit Test that includes the following lines:
Dim nullarray As Integer()()
Assert.AreEqual(nullarray.ToString(False), "Nothing")
The variable "nullarray" will obviously be null when ToString is called (ToString is an extension method, which is the one I am testing). This is by design, because the purpose of this specific unit test is to make sure that my ToString extension
method handles null values the way I expect. The test runs fine, but Visual Studio 2013 gives includes the following warning:
Variable 'nullarray' is used before it has been assigned a value. A null reference exception could result at runtime.
This warning is to be expected, and I don't want to stop Visual Studio 2013 from showing this warning or any other warnings, just this specific case (and several others that involve similar scenarios). Is there any way to mark a line or segment
of code so that it is not checked for warnings? Otherwise, I will end up with lots of warnings for things that I am perfectly aware of and don't plan on changing.
Nathan Sokalski [email protected] http://www.nathansokalski.com/

Hi Nathan Sokalski,
Variable 'nullarray' is used before it has been assigned a value. A null reference exception could result at runtime.
Whether the warning above was thrown when you built the test project but the test run successfully? I assume Yes.
Is there any way to mark a line or segment of code so that it is not checked for warnings?
There is no built-in way to make some code snippet or a code line not be checked during compiling, but we can configure some specific warnings not to be warned during compiling in Visual Basic through project Properties->Compile
tab->warning configurations box.
For detailed information, please see: Configuring Warnings in Visual Basic
Another way is to correct your code logic and make sure the code will not generate warning at runtime.
If I misunderstood you, please tell us what code you want it not to be checked for warnings with a sample so that we can further look at your issue.
Thanks,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Unit Testing

Hi All,
I would like to inform to all, can any one explain to me the concept of Unit testing in FICO and how it should be drawn? If possible send any dcoumentation for this focus to my mail id: [email protected]
Thanks with regards,
Bala

Hi
refer below reward if helps
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
We use different software during testing. Most commonly use are
Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:-
1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the data)
http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
Unit test issues
The unit tools test all SAP development work that handles business object processing for the connector. Also, the unit test tools enable you to test the interaction of your work with the ABAP components of the connector. The test tools allow you to test your development work as an online user (real-time) only.
Note:
It is important to understand the differences between testing the connector as an online user and testing the connector as if operating as a background user.
The differences between testing the connector as an online user or as a background user are described as follows:
Memory--When testing a business object, the connector must log into the SAP application.
      The connector runs as a background user, so it processes in a single memory space that is never implicitly refreshed until the connector is stopped and then restarted (therefore it is critical in business object development to clear memory after processing is complete). Since you are an online user, memory is typically refreshed after each transaction you execute.
      For more information, see Developing business objects for the ABAP Extension Module. Any problems that may occur because of this (for example, return codes never being initialized) are not detected using the test tool; only testing with the connector will reveal these issues.
Screen flow behavior--Screen flow behavior is relevant only when using the Call Transaction API. The precise screen and sequence of screens that a user interacts with is usually determined at runtime by the transaction's code. For example, if a user chooses to extend a material master record to include a sales view by checking the Sales view check box, SAP queries the user for the specific Sales Organization information by presenting an additional input field. In this way, the transaction source code at runtime determines the specific screen and its requirements based on the data input by the user. While the test tool does handle this type of test scenario, there is a related scenario that the test tool cannot handle.
      SAP's transaction code may present different screens to online users versus background users (usually for usability versus performance). The test tool only operates as an online user. The connector only operates as a background user. Despite this difference, unit testing should get through most of the testing situations.

Problem creating unit testing repository (and workaround)

I tried to create the unit testing repository with a user that had all the required system privileges granted through a different role other than RESOURCE and CONNECT roles, and who wasn't explicitely granted CREATE VIEW, but inherited it through the custom role. However the check in SQL Developer is explicitely for the RESOURCE and CONNECT roles (regardless of what privileges they have granted to them in whichever database version past, present or future) and for CREATE VIEW privilege granted direct to the user:
SELECT DECODE (roles.required_role_count + privs.required_priv_count,
               3, 1,
               0)
          AS basic_privs_granted
FROM (SELECT COUNT (*) AS required_role_count
          FROM user_role_privs
         WHERE granted_role IN ('CONNECT', 'RESOURCE')) roles,
       (SELECT COUNT (*) AS required_priv_count
          FROM USER_SYS_PRIVS
         WHERE privilege IN ('CREATE VIEW')) privsI found this SQL contained within the sqldeveloper/extensions/oracle.sqldeveloper.unit_test.jar in an XML file: oracle/dbtools/unit_test/manage_user/UserSql.xml and replaced the SQL with one that actually checks for the specific system privileges:
SELECT DECODE (required_sys_priv_count,
               10, 1,
               0)
          AS basic_privs_granted
FROM
       (SELECT COUNT(*) AS required_sys_priv_count FROM
         (SELECT privilege
            FROM role_sys_privs
           WHERE privilege IN ('CREATE CLUSTER','CREATE INDEXTYPE','CREATE OPERATOR','CREATE PROCEDURE','CREATE SEQUENCE','CREATE SESSION','CREATE TABLE','CREATE TRIGGER','CREATE TYPE','CREATE VIEW')
          UNION
          SELECT privilege
            FROM user_sys_privs
           WHERE privilege IN ('CREATE CLUSTER','CREATE INDEXTYPE','CREATE OPERATOR','CREATE PROCEDURE','CREATE SEQUENCE','CREATE SESSION','CREATE TABLE','CREATE TRIGGER','CREATE TYPE','CREATE VIEW')))This enabled me to bypass that check when creating the respository. I don't know if all these privileges are actually required by the unit testing repository or not, so maybe the above list can be reduced...
Edited by: RDB on Mar 1, 2013 2:24 PM

Hi Sai Vineeth,
First of all, I appreciate your elaborate way of framing the question. That itself helps others to comment.
On the first two questions, I am sure you'll be able to follow the answers provided and take care of your concerns.
On your question 3), an additional piece of information that should bring smile to you
Whether the Test is to happen in DEV or QAS or whatever 'System Role' is dependent on the Test Plan.
So, if you have two distinct Test Plans, one for Unit Tests and the other for Integration Tests, which should be the case, as usual, you can certainly point the System Role to DEV or QAS as required.
Feel free to pose any other query as well.
Best regards,
Srini

Abt unit test plan

Similar Messages

Maybe you are looking for