Unit Testing / Integration Testing

Hi all
Can somebody provide links to SAP testing....
Can anybody define & write down the step by step details on carrying out unit testing, integration testing and user acceptance testing...How it is done..which systems..tools..test scripts / test cases etc

hi,
For all kinds of testing the first thing is to enumerate the scenarions i.e preparing a list of scenarions that need to be tsted. this wud include the test data and also the desired results. templates are provided by the consultants to the end users. thse templates have a description of the scenarios, the data used, the transacion codes, the docs generated and if the desired results were obtained. thse need to be certified by the concerned.
integration and unit tsting can be done on the same or different clients depanding on system landscape. user accptance testing is generally after the interfration tests have been satisfactorily conducted. different knds of users are asked to do the tests once their id roles and profiles are created. this phase shud be handled as if live production envirionment.
saurabh

Similar Messages

Unit Tests / Integration tests

Hi Experts,
I am planning to enchance the existing extract structure in R/3 by including new fields.
After that, I need to enhance my structures and existing infoproviders in BW.
I have just finished the blue printing phase.
I would like to know what are the unit tests / test scenarios / test plans / test cases that I need to consider? Is there a list of standard unit tests?
Also, what about integration tests?

hi,
Unit testing is the one in which the developer himself test the code.
In Unit testing the developer will test whether all the statements will execute based on different conditions.
There should not be any dead code after Unit test.
Dead Code means, for any given combination the control will not go to the statement.
you can go thru the following links
http://en.wikipedia.org/wiki/SAP_Implementation
http://hosteddocs.ittoolbox.com/CM021805.pdf
Look at the below link
http://softwarefinder.mbtmag.com/search/for/Techrepublic-Cost-of-SAP-Implementation.html
refer to the following links.
http://blogs.ittoolbox.com/eai/implementation/archives/gui-windows-types-unit-test-template-12961
Integration testing is usually where the func team run processes end to end. If security is involved then generally you are validating that the roles contain required transactions, there aren't any gaps where roles can't support the processes. You may want to test org levels and +ve and -ve test controls here but it really depends on your implementation. Most security testing is usually done in UAT but you would preferably have func team using real end user roles in IT, though generally not in the first passes where they validate their config
Ramesh

Unit testing and integration testing

hello 2 all,
what is the diff bet unit and integration testing? in sap what is unit teesting consists of and integration testing consists of what?
is this the work of test engineers r whose work is this?
take care
love ur parents

Hi Sameer,
Unit Testing
A unit test is a procedure used to validate that a particular module of source code is working properly from each modification to the next. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is
separate from the others; constructs such as mock objects can assist in separating unit tests. This type of testing is mostly done by the developers and not by end-users.
Integration testing
Integration testing can proceed in a number of different ways, which can be broadly characterized as top down or bottom up. In top down integration testing the high level control routines are tested first, possibly with the middle level control structures present only as stubs. Subprogram stubs were presented in Section 2 as incomplete subprograms which are only present to allow the higher level control routines to be tested. Thus a menu driven program may have the major menu options initially only present as stubs, which merely announce that they have been successfully called, in order to allow the high level menu driver to be tested.
Top down testing can proceed in a depth-first or a breadth-first manner. For depth-first integration each module is tested in increasing detail, replacing more and more levels of detail with actual code rather than stubs. Alternatively breadth-first would proceed by refining all the modules at the same level of control
throughout the application. In practice a combination of the two techniques would be used. At the initial stages all the modules might be only partly functional, possibly being implemented only to deal with non-erroneous data. These would be tested in breadth-first manner, but over a period of time each would be
replaced with successive refinements which were closer to the full functionality. This allows depth-first testing of a module to be performed simultaneously with breadth-first testing of all the modules.The other major category of integration testing is bottom up integration testing where an individual module is
tested from a test harness. Once a set of individual modules have been tested they are then combined into a collection of modules, known as builds, which are then tested by a second test harness. This process can continue until the build consists of the entire application.
In practice a combination of top-down and bottom-up testing would be used. In a large software project being developed by a number of sub-teams, or a smaller project where different modules were being built by individuals. The sub-teams or individuals would conduct bottom-up testing of the modules which they were
constructing before releasing them to an integration team which would assemble them together for top-down testing.
I think this will help.
Thanks ,
Saptarshi

Unit Testing and Integrating testing In HR

Dear Sap Gurus,
Would you be kind enough to give me an example of unit testing and integrating testing?? what do you test, eg..TC and what else.. what happened.??. And also an example of Integrating testing ..and an example ....I know what unit and integrating test is ..and with a good example, i will have a great idea about it ...thanks a lot.

Hi Pooja
Unit Testing:
A process for verifying that software, a system, or a system component performs its intended functions.
Unit transactions are tested against their own specifications and design documents.
Integration Testing
An orderly progression of testing in which software elements, hardware elements or both are combined and tested until the entire system has been integrated.
Integration tests deal mainly with the testing of cross-application process chains in addition to transactions and business processes. The process models and the test cases derived from these form the basis of these tests.
Regards
Vijay

Unit testing or integration testing?

Here it says that this example is more of an explanation of framework than best practice because of the conflation of integration/unit testing concepts: http://docs.flexunit.org/index.php?title=Using_Asynchronous_Startup
My question is, how do you define a line here between unit testing and integration testing? What kind of UI components asynchronous tests are then considered to be unit tests and not yet integration tests? Many books recommend having 100% code coverage with unit tests. How would this example look like, to be considered only a unit test and not integration test?

The question about which levels of testing to do are really dependent upon you. Let me explain a bit more.
If you are building an application, and only an application, then functional testing probably covers most of your needs. In an application environment, you have a relatively narrow pathway of options and interactions that a user might follow. So long as you test those options well, your app will probably work as well.
Where I see the real value of unit testing is testing for the unknowns. If you have a class that will be used in multiple applications in multiple ways, or perhaps it is intended to be a reusable class where others in your organization will use it in the future, then you want lower level testing. You want to have the best coverage you can because you want to know that, regardless of the way someone chooses to use the code, it will likely function or at least fail gracefully.
The same is true for integration. If I am creating a Flex component, then I can unit test part of it, but not all. So, I want to use integration tests to ensure that it works in as many circumstance as possible. Further, Flex components have a life cycle, so testing them when they are not on the display list isn't really a valid test..
So, to summarize, I see unit and integration w/Flex about testing possibilities and trying to achieve realistic code coverage for known and possible use cases. I see functional testing as testing those components in very specific use cases.
Which do you need? Depends. Are you developing reusable components across (n) projects, likely the first 2 and maybe the last. Are you an application developer testing that an application works in documented business cases? Just functional will likely work.
Hope that helps,
Mike

Unit testing and system integration testing for crystal report

Hi gurus,
I am creating crystal report by oracle procedure, will you please tell me how to do unit testing and system integration testing? appreciate very much.

The focus of this forum is report design. The actual testing of reports would be subject to your own internal policies and procedures.
Jason

Unit testing, integration and functional testing

Hello all,
I would like to know the difference between Unit testing, integration and functional testing. And also what are the testing tools that are more commonly used?
Thanks,
Maxx

Hi,
    Unit testing :
                A complete cycle of each module will be tested
                ie for PP Right from requirements to planned orders /production orders
                confirmation .
    Integration testing:
                Here cross module testing will be carried out.
                 ie PP and MM integration
                    After confirming production order a GR is made /billing is carried out
                    and delivered.
      Functional testing:
                This testing is carried out to see whether the system can with stand l the loads during processing by users.
                Stress test and volume test.
            Regards,
            nandha

Difference between unit testing and integration testing

What is the difference between unit testing and integration testing in SAP? Is unit testing takes place in Dev client and integration testing takes place in QA system?
Please clarify
thanks

Hello Krishen,
unit testing means veryfiingsmall / the smallet pieces of software, while integration testing checks the overall functionality of applications. Within the AS ABAP the tool ECATT + manual tests is used for integration tests and the ABAP Unit language integration for unit testing.
When, Who, Where tests are carried out is ultimately a personal decision. As unit tests are operate even under heavy development they are often the first choice for developers, but the unit tests can also serve for regression tests over a long period. Integration tests tend too be created and executed in later stages as they require often a certain majurity of the software under test.
Beside the mentioned links you may check out ABAP Unit infos also in the Wiki.
https://wiki.sdn.sap.com/wiki/display/HOME/ABAP+Unit
Best Regards
Klaus

SOLMAN-Integration Test

Dear gurus,
We defined business processes in Blueprint (SOLAR01)
against that we created a test plan and test packages and done the unit testing.
Now we have to do integration test.which cut across all modules.
whether separate business process to be created in SOLAR01 to create Test plan and test packages or can we use the exisiting business process itself.If it so, how to define a test plan by combining all module business process..
For example:
Take the Scenario Order To Cash Cycle.
which cut across MM,SD,PP,QM,CO,FI transactions
In the blueprint no where we maintain in this sequence. Because the blueprint is meant for individual module specific.
so what is the recommended method for integration test.
Should i create Each Integration Scenario as Separate Business Process in SOLAR01 or should i select thr transacion alone from different business process of existing Blueprint.
Pls guide me.

Thanks Prabhakar,
I am aware of this, but this gives me details for one test plan. Even when I use STWB_2, it gives me summary of all the test plans, and for status overview I have to go in each and every test plan.
I am looking for some way out to generate the status overview of multiple test plans together in same screen, for reporting purpose.
Any suggestions?
Thanks,
Smita

Scenario Testing vs. Integration Testing

Hi,
I am really confused with all the Testing lingo. There are so many different types of testing. They all sound like one another. Can somebody please clarify for me the difference btwn scenario testing and integration testing. A definition of each with a brief explanation would be nice.
Thanks
<b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Hi Ali,
Testing is actually the process of exercising or evaluating a system or a system component by manual or automated means to verify that it satisfies specified requirements. It is the process of executing a program with the intent of locating errors.
There are certain levels of testing as below:
1) Unit Testing or Component Testing or White Box Testing or Scenario Testing
2) Integration Testing or Interface Testing
3) System Testing
So, Scenario or Unit testing is taken care by the developer by executing the particular piece. Example is Developer wrote one program to display the list of vendors details. So, the developer tests whether the program is displaying the data correctly and in the correct format meeting the requirements.
Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one unit. In a realistic scenario, many units are combined into components, which are in turn aggregated into even larger parts of the program. The idea is to test combinations of pieces and eventually expand the process to test your modules with those of other groups. Eventually all the modules making up a process are tested together.
Integration testing (sometimes called Integration and Testing, abbreviated I&T) is the phase of software testing in which individual software modules are combined and tested together as a group.The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items.
Example: A third party system sends vendor data file into our unix box. Our application program read the file and uploads the data and posts to different tables there by creating some document numbers.
Hope this helps.
<b><REMOVED BY MODERATOR></b>
Thanks,
Srinivasa
Message was edited by:
Alvaro Tejada Galindo

REG:REGRESSION & SYSTEM INTEGRITY TEST

Hi experts,
i have one question i dont know it may be basic question. i am new to xi/pi can you please tell me
how we test & what the purpose of the REGRESSION TEST,SYSTEM INTEGRITY TEST,PERFORMANCE TEST
what are the differences between these three test in pi
thanks in advance
koti

Hi
From the point of view of PI landscape and testing methodologies :
Performance testing
1.To Test the systems load tolerance .Its purely physical testing and no application logic is tested in this.One case may be to check the system performance like how much time is taken if multiple users assess the system or say create orders using the interface.
2.There may be several ways u can design an interface to make the business logic to work.(say with BPM or without BPM).So in PT you can evaluate system performance and decide on which approach is best suited.
3. It might be useful to fix any hardware sizing issues also.
4.Usually done in pr- prod system say after a system refresh or migration etc.
System Integration Testing--
1. To test end to end business logic and functionality when all the systems in the data flow are connected and individual unit test is already done (say ECC,PI and third party ).
2. helps is checking the connectivity, execution of functionality.Basically it can be a functionality test.
3.Done after Dev and before User acceptance testing.
Regression testing----
1. Its done when there are changes made to functionality/data , before and after test scripts are prepared and executed.
2.its helps in checking if the changes made will effect any exisiting functionality ,basically before and after the change the existing functionality should not effect but the required changes should reflect.
3.Done after a fix in code and before moving it to prod.
You can refer this like alsohttp://wiki.sdn.sap.com/wiki/display/ERPLO/TypesofTestings
Best Regards,
Srinivas

Docs on integration testing

please send me docs on integration testing with atleast one complete scenerio

Hi Karunakar,
Integration testing - It is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.
Integration testing takes as its input modules that have been checked out by unit testing, groups them in larger aggregates, applies tests defined in an Integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
Unit testing - One part or the whole part of transfer rules , update rules, etc..
Integration testing - The whole data flow cycle to be tested
This link will give u detailed description
http://en.wikipedia.org/wiki/Software_testing
Stress testing in BI..
/people/mike.curl/blog/2006/12/05/how-to-stress-test-bw-the-easy-way
REFER THIS REG CATT
http://help.sap.com/saphelp_erp2005/helpdata/en/d7/e21221408e11d1896b0000e8322d00/frameset.htm
Check this doc on Unit Testing
unit testing
Look at the threads below :
Testing Methods in BW
Unit Testing in BW
How to do testing in BW
Hi...BW testing
Re: Hi...BW testing
Hi...BW testing
Pls refer following links...
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e210c8408e11d1896b0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3c/aba235413911d1893d0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e2123b408e11d1896b0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d7/e2123b408e11d1896b0000e8322d00/frameset.htm
Hope it helps you!
****Assign Points If Helpful****
Regards,
Ravikanth

My Macbook aliminium unibody from late 2008 will not boot. I reach the grey screen with the apple icon and the spinning grey gear. I used disk utility to boot it but it said integrity test failed. I don't know what to do can anyone please help?

My Macbook aliminium unibody from late 2008 will not boot. I reach the grey screen with the apple icon and the spinning grey gear. I used disk utility to boot it but it said integrity test failed. I don't know what to do can anyone please help?

Sounds like you may have a harddrive issue. You are probably going to need to get that changed out and then install the OS X again to get it going.

[svn:osmf:] 13357: 1) Modified a integration tests to correspond with the change to PluginInfo becoming a class .

Revision: 13357
Revision: 13357
Author:   [email protected]
Date:     2010-01-07 17:05:22 -0800 (Thu, 07 Jan 2010)
Log Message:
1) Modified a integration tests to correspond with the change to PluginInfo becoming a class.
2) Modified the DFXPParser class in the CaptioningPlugin to use the new TimeUtil class in the framework.
Modified Paths:
    osmf/trunk/plugins/CaptioningPlugin/org/osmf/captioning/parsers/DFXPParser.as
    osmf/trunk/plugins/CaptioningPluginIntegrationTest/src/org/osmf/test/captioning/TestCapti oningPluginInfo.as
    osmf/trunk/plugins/MASTPluginIntegrationTest/src/org/osmf/test/mast/TestMASTPluginInfo.as
    osmf/trunk/plugins/MASTPluginIntegrationTest/src/org/osmf/test/mast/managers/TestMASTCond itionManager.as

DSP Test Integration Toolkit doesn't work with CCS4

Hello,
After good experience with CCS2 & DSP Tollkit I've got CCS4 from TI.
There is no connection from the toolkit to this CCS version.
Is there is new version of the toolkit or some support ?
Regards.
Vladimir

Vladimir,
What Version of LabVIEW and the DSP Module are you using?
This document in the LabVIEW help may provide some help:
Using the TI Code Composer Studio Toolchain with the DSK6713 Example Target (Microprocessor SDK)
This Tutorial on our website also talks quite a bit about the Code Composer Studio:
Connecting to Texas Instruments DSPs Using the LabVIEW DSP Test Integration Toolkit
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Unit Testing / Integration Testing

Similar Messages

Maybe you are looking for