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

Similar Messages

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

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

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

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

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 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 test and bug fixing

hai i m an abap devoloper i need to know how to fix a bug and how unit test is evaluated or how its done can u briefly explain me ,i know errors detactin thru debuggger then whats for unit test can u explain me this concept

Unit (Functional) TestingSAP Component or Feature Available
Services
   1. Unit (functional) testing
Unit Testing
   1. A process for verifying that software, a system, or a system component performs its intended functions.
   2. Unit transactions are tested against their own specifications and design documents.
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 separately 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.
Integration Testing
   1. An orderly progression of testing in which software elements, hardware elements or both are combined and tested until the entire system has been integrated.
   2. 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.

Monitoring and unit testing

how to do monitoring and unit testing the interface from Runtime work bench.

Hi,
RWB is a tool in SAP XI/PI which helps you to monitor the messages.
please find the below linnk
http://help.sap.com/saphelp_nw04/helpdata/en/88/21bc3ff6beeb0ce10000000a114084/content.htm
please search on SDN or http://help.sap.com
Whereas RWB runs on Java stack of XI. In RWB you can monitor message on Integration server and Adapter Engine as well
RWB we have component monitoring and message monitoring
i) component monitoring you can monitor the status of ur communication channel
ii) message monitoring you can monitor ur message in the XI.
Regards
srinivas

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 with Microsoft Sharepoint Emulators and Fakes with Visual Studio 2013

Hi All,
I have created Test Project and now creating Test cases for Sharepoint. I found a link on MSDN which suggests using Fakes framework but it supports VS2012 and I am using Visual Studio 2013.
So how can I use it with VS2013 or is there any other way with which I can implement the Test cases with VS2013.
Please suggest.
Thanks in advance.
Himanshu Nigam

Hi HimanshuNigam,
According to your descrition, my understanding is that you want to use Fakes framework to create test case for SharePoint project in Visual Studio 2013.
If you want to test using Fakes Framework, you can use the codeplex extension to achieve it. It supports Visual Studio 2013.
Here is a detailed article for your reference:
Better Unit Testing with Microsoft Fakes
About how to include the Nuget package, you can use the package with the link below:
NuGet Package Manager for Visual Studio 2013
Installing NuGet
If you still have question about this issue, I suggest you can create a post in Visual Studio, more experts will help you and you can get more detailed information from there:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio%2Cvsarch%2Cvsdbg%2Cvstest%2Cvstfs%2Cvsdata%2Cvsappdev%2Cvisualbasic%2Cvisualcsharp%2Cvisualc
Best Regards
Zhengyu Guo
TechNet Community Support

Unit Testing of servlets and jsp by Junit

hi,
suggest me how to do the unit testing by junit!
thanks in advance

Or abstract the business logic away from the actual servlets themselves (always a good idea) and test those classes outside the context of a servlet framework.
That limits the code that actually is impacted by being a servlet to the absolute minimum (essentially parameter passing).

Unit Testing and Integrating testing In HR

Similar Messages

Maybe you are looking for