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

Similar Messages

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

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

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

Purpose of UVT and integrations tests

Hello
Can you please explain me the purpose of User validation and integration tests?
In which system are these tests conducted?
Thanks

Hi,
These Tests are done in
1)User Tests-In Dev-Done by Developer
2)IntegrationTest - In Quality.-Done by Third Party or user.
The Purpose of it ..........
1)There is Gap in understanding of the User Requiement and what wehave developed.
2)For Ducumentation purpose so that if there is ny clarifiction in future we can always refer the UT/IT.
3)Security Reasons,impact
4)Authorization Reasons,impact.
5)To check the Quality of Data and the Amount of Validation done.
6)To Cross check all the Scenerios as per Requieement.
7)if any Programs are used ,the impact of the same.
Rgds
SVU

System test and Pilot test

Hi All,
Kindly provide some information regarding "System test and Pilot test".
Thanks in advance.

Hi Friends,
This is the information I got from my friend who is working as a Tester.
System Testing :-
This type of testing is exactly opposite from the Unit Testing. System Testing is used to test the entire functionality at the same time.
Pilot Testing :-
Generally, a normal testing is done by the programmers. After this, the product is sent to the internal client ( i.e. other users inside the same concern ) for testing. This method of testing is called Pilot Testing.

Stress and Integration Testing

Hello,
Can anybody provide me some documents on Integration and Stress Testing with examples. I searched the forum but found only a general view of Integration testing.
Thanks

hi sap bw begineer,
use this links
https://www.purdue.edu/onepurdue/contribute_pdf/sap_integration_testing_orientation.pdf
http://www.sucid.com/sucidload.shtml
with hopes
Raja Singh

When do u go for elementary test and combined test(rsrv)

hi all,
Can anyone explain me with an realtime scenario ? when do we go for elementary test in rsrv trns code and combined test.
thanxs
hari

hi hari,
RSRV is used for analysis and repair of all BW objects.You can perform consistency checks on the data and metadata stored in BW System.RSRV tests the foriegn key relationships between the individual tables of the enhanced starschema of the BW system
There are 2 types of tests
1.Elementary Tests- these tests are related to master data,transaction data,ODS objects,Hierarchies.database(indices,parametres,statistics),aggregates,PSA tables and documents.
2.Combined Tests-This test determines which elementary tests are performed according to the parametres entered.
Hope this helps!
partha

SAP Testing and normal testing

How different is SAP testing with other testing, is it enough to know the normal testing procedure and few tools like mercury QTP, winrunner, loadrunner, etc...
Please throw some light on this..
Thanks-

Hello Rahul Saxena,
SAP testing is also simillar to other applications testing. We can use many testing tools like Mercury QTP, QC , winrunner, loadrunner, Test Director etc...
Thanks,
Greetson

Recommended Site for speed tests and other tests.

Ive posted this site before as a response to a thread, but I think many people need to start using it.
Ive found it very helpful and it explains many things, and runs all kids of prediction tests.
IP profile tests etc.....
http://www.kitz.co.uk/adsl/max_speed_calc.php
Check it out.
Netgear Setup

The particular link you mention is already well subscribed ....
you found it.... before it was lost...

How do i remove Monkey Test and Time Test malwares in my lenovo a328?

I tried different file/root managing apps (ex: es file explorer and app uninstaller) to no avail. AVG even detected it as a "potentially unwanted program" . it can also be detected using x-plore app. i also tried using this app to uninstall these two malwares but keep on coming back everytime i check. need help...

Hi,
Welcome to the forum.
Considering that this is an Android phone, removal is a different process from what we usually see on this forum.
The best advice that I can offer at this time is to install Free Malwarebytes Mobile, and see if that is able to identify it.
https://www.malwarebytes.org/mobile/
If the app is able to find it, but not remove, posting here for their Android experts and staff will probably get you the help you need. They have researchers on staff who may be interested in this.
https://forums.malwarebytes.org/index.php?/forum/131-malwarebytes-anti-malware-mobile-help/

Difference between Real Application Testing and Application Testing Suite?

We need to find out average time to execute critical reports. Some reports takes about 24 hours to execute. We want to predict the times of future reports after benchmarking our current DB.
(1.) Which of the 2 should we use (RAT or ATS)?
(2.) What are the differences between the 2?
(3.) Can these products be used in both 10g and 11g DBs?
(4.) Are these 2 ''options'' that come with the DB? or
(5.) Do we have to purchase them separately and install separately?
(6.) Does these tools have Windows interfaces?

Thanks aamat.
Most of our DBs are and will be in 10g. I think it will take at least a year or two to move to 11g. So we are basically stuck with 10g.
So you’re saying we need a 11g DB to run RAT. I.e. you have to install RAT in a 11g. That wont suite our requirements since our DBs are in 10g.
About ATS: The most demanding/frequent requirement from our prospective customers is:
> "We create an ad-hoc report query. How do we find out the time it will take to execute it?"In order to solve this we are hoping to suggest this to our customers:
1.) Replicate the servers and DB (with real data) in another identical machine.
2.) Select about 10 report queries which normally takes a long time to execute.
3.) Execute them and get the times (For single and multiple users).
4.) These will form the benchmark.
*[Q1.]* Now, can our prospective users, use ATS do this. I.e. Can they, the users on their own operate ATS (of course after giving them training)?
*[Q2.]* Can ATS use the output of the previous (i.e. benchmark) SQL queries (with live data) and if given another SQL, estimate the time it will take to execute it?
-- i.e. can ATS compare the tables, SQL query and times of past results and give us an estimate for our new query?
*[Q3.]* If this is not possible in ATS can it be done it RAT? In this case we will have to demand that they upgrade to 11g.
Edited by: Channa on Aug 26, 2010 6:56 AM

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

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

Unit tests and QA process

Hello,
(disclaimer : if you agree that this topic does not really belong to this forum please vote for a new Development Process forum there:
http://forum.java.sun.com/thread.jspa?forumID=53&threadID=504658 ;-)
My current organization has a dedicated QA team.
They ensure end-user functional testing but also run and monitor "technical" tests as well.
In particular they would want to run developer-written junit tests as sanity tests before the functional tests.
I'm wondering whether this is such a good idea, and how to handle failed unit tests:
1) Well , indeed, I think this is a good idea: even if developer all abide by the practice of ensuring 100% of their test pass before promoting their code (which is unfortunately not the case), integration of independant development may cause regression or interactions that make some test fail.
Any reason against QA running junit tests at this stage?
However the next question is, what do they do with failed tests : QA has no clue how important a given unit test is with regard to the whole application.
Maybe a single unit test failed out of 3500 means a complete outage of a 24x7 application. Or maybe 20% of failed tests only means a few misaligned icons...
2) The developer of the failed package may know, but how can he communicate this to QA?
Javadocing their unit testing code ("This test is mandatory before entering user acceptance") seems a bit fragile.
Are there recommended methods?
3) Even the developer of the failed package may not realize the importance of the failure. So what should be the process when unit tests fail in QA?
Block the process until 100% tests pass? Or, start acceptance anyway but notify the developper through the bug tracking system?
4) Does your acceptance process require 100% pass before user acceptance starts?
Indeed I have ruled out requiring 100% pass, but is this a widespread practice?
I rule it out because maybe the failed test indeed points out a bad test, or a temporary unavailability of a dependent or simulated resource.
This has to be analyzed of course, as tests have to be maintained as well, but this can be a parallel process to the user acceptance (accepting that the software may have to be patched at some point during the acceptance).
Thank you for your inputs.
J.

>
Any reason against QA running junit tests at this
stage?
Actually running them seems pointless to me.
QA could be interested in the following
- That unit tests do actually exist
- That the unit tests are actually being run
- That the unit tests pass.
This can all be achieved as part of the build process however. It can either be done for every cm build (like automated nightly) or for just for release builds.
This would require that the following information was logged
- An id unique to each test
- Pass fail
- A collection system.
Obviously doing this is going to require more work and probably code than if QA was not tracking it.
However the next question is, what do they do with
failed tests : QA has no clue how important a given
unit test is with regard to the whole application.
Maybe a single unit test failed out of 3500 means a
complete outage of a 24x7 application. Or maybe 20%
of failed tests only means a few misaligned icons...
To me that question is like asking what happens if one class fails to build for a release build.
To my mind any unit test failure is logged as a severe exception (the entire system is unusable.)
2) The developer of the failed package may know, but
how can he communicate this to QA?
Javadocing their unit testing code ("This test is
mandatory before entering user acceptance") seems a
bit fragile.
Are there recommended methods?Automatic collection obviously. This has to be planned for.
One way is to just log success and failure for each test which is gathered in one or more files. Then a seperate process munges the result file to collect the data.
I know that there is a java build engine (add on to ant or a wrapper to ant) which will do periodic builds and email reports to developers. I think it even allows for categorization so the correct developer gets the correct error.
>
3) Even the developer of the failed package may not
realize the importance of the failure. So what
should be the process when unit tests fail in
QA?
Block the process until 100% tests pass? Or, start
acceptance anyway but notify the developper through
the bug tracking system?
I would block it.
4) Does your acceptance process require 100% pass
before user acceptance starts?
No. But I am not sure what that has to do with what you were discussing above. I consider unit tests and acceptance testing to be two seperate things.
Indeed I have ruled out requiring 100% pass, but is
this a widespread practice?
I rule it out because maybe the failed test indeed
points out a bad test, or a temporary unavailability
of a dependent or simulated resource.Then something is wrong with your process.
When you create a release build you should include those things that should be in the release. If they are not done, missing, have build errors, then they shouldn't be in the release.
If some dependent piece is missing for the release build then the build process has failed. And so it should not be released to QA.
I have used version control/debug systems which made this relatively easy by allowing control over which bug/enhancements are included in a release. And of course requiring that anything checked in must be done so under a bug/enhancement. They will even control dependencies as well (the files for bug 7 might require that bug 8 is added as well.)

Unit testing and integration testing

Similar Messages

Maybe you are looking for