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.

Similar Messages

[svn:osmf:] 12425: Extending unit tests, and fixing a bug.

Revision: 12425
Revision: 12425
Author:   [email protected]
Date:     2009-12-03 04:22:59 -0800 (Thu, 03 Dec 2009)
Log Message:
Extending unit tests, and fixing a bug.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/CompositeMetadata.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestCompositeMetadata.as

[svn:osmf:] 12257: Extending trait resolver related unit tests, and fixing found malfunctions.

Revision: 12257
Revision: 12257
Author:   [email protected]
Date:     2009-11-27 13:01:04 -0800 (Fri, 27 Nov 2009)
Log Message:
Extending trait resolver related unit tests, and fixing found malfunctions.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/media/DefaultTraitResolver.as
    osmf/trunk/framework/MediaFramework/org/osmf/media/MediaElement.as
    osmf/trunk/framework/MediaFramework/org/osmf/media/MediaTraitResolver.as
    osmf/trunk/framework/MediaFramework/org/osmf/utils/MediaFrameworkStrings.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/audio/TestAudioElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/video/TestVideoElement.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/MediaTraitResolverBaseTestCase .as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestDefaultTraitResolver.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaTraitResolver.as

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

[svn:osmf:] 11199: Sample clean up and bug fixing.

Revision: 11199
Author:   [email protected]
Date:     2009-10-27 13:56:22 -0700 (Tue, 27 Oct 2009)
Log Message:
Sample clean up and bug fixing.
Modified Paths:
    osmf/trunk/apps/samples/framework/CuePointSample/src/CuePointSample.mxml

At least in the version I was using it was, quite literally. Horrible.
Invalid, unsemantic, not cross-browser, and subject to quirks mode rendering.
That isn't necessarily a comment on the developers of the system as a whole. Just those who created the HTML and JS. And, who knows, perhaps was improved in later versions.
From my experience with other CMS systems, though, there is sufficient abstraction to fix much of this, if the templates for the HTML and JS can be located.
I'm hoping that SAP is the same, that there are places to look for the HTML that creates major UI components.
This seems useful anyway, since customising is more effective if the templates themselves can be changed at that level.
This also carries over to the IDE - where the sample apps that could be created also generated invalid or unsemantic HTML and JavaScript in my tests. (setting aside my killing my server in my first test of field submission just by pasting a few kilobytes of text in the field )
Anyway, certainly front-end is not a comment on system as a whole, but lightweight and valid HTML makes styling much easier, so if I could figure out how to fix that, it'd be lovely.
P.S. - this forum itself uses "color: windowText" for text areas without setting background-color: window.
Kind of sloppy, easily fixed on my side (where I use a dark UI theme) by overriding the site style.

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

[svn:osmf:] 10648: Adding first MAST unit tests and added some ASDocs

Revision: 10648
Author:   [email protected]
Date:     2009-09-28 10:28:12 -0700 (Mon, 28 Sep 2009)
Log Message:
Adding first MAST unit tests and added some ASDocs
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/.actionScriptProperties
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/MediaFrameworkTests.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/adapter/MASTAdapter.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTDocumentProcessedEvent. as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTDocumentProcessor.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTLoadedContext.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTLoader.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/managers/MASTConditionManager.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/MASTTestConstants.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/loader/
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/loader/TestMASTLoade r.as
    osmf/trunk/plugins/MASTLib/
    osmf/trunk/plugins/MASTLib/.actionScriptProperties
    osmf/trunk/plugins/MASTLib/.flexLibProperties
    osmf/trunk/plugins/MASTLib/.project
    osmf/trunk/plugins/MASTLib/src/

These are automated emails from the OSMF forums. To unsubscribe, go here:
http://forums.adobe.com/community/opensource/osmf/commits
-- Brian

Vibe Z2 Pro (K920) stock ROM improvements and bug fixes

Phone info: Lenovo K920, Android 4.4.2, K920_ROW_S133_141010 I've already posted this message, but, probably, to the wrong forum section. Hello to all I hope that if it is the official Lenovo forum, the respectable developers already read it from time to time & some thoughts about Vibe Z2 Pro stock software improvements and bug fixes will be useful for them. Interface1) "Double tap to wake" feature is, probably, the most requested one.2) There is very long response period between the long pressing "Menu" button and the showing of the earlier executed applications list. Even then Settings > Accessebility > [Touch & hold delay] is set to "Shot". I'd better to cut this delay twice.3) "Clear all" function in the the earlier executed applications list sometimes seems doesn't work properly: I press the button, clearance process indicator is rotating, but the list isn't empty.4) The system font is lengthened by vertical axis & it looks worse then the corresponding font on nexus devices. Lockscreen1) Lockscreen crashes when Poweramp with the default settings is playing a song (Poweramp > Settings > Lock Screen > Enable Android Lock Screen = true). Probably, this is a Poweramp bug, not K920 ROM (The Rocket Player with the same functionality works well), but who knows...2) There will be a good idea to realize option "Disable change lockscreen picture by swype" somewhere in Settings, because such an involuntary change take place regularly. Stock Camera app1) As far as I know, Samsung Galaxy S5 has an HDR option for recording a video. It would be cool to implement this feature (moreover, if I'm not mistaken, K920 has the same camera hardware).2) In professional mode I can drag "Photo camera" icon left and this will result in appearance the five curves of settings (like a Solar system) - just as in Nokia Camera for Nokia Lumia phones. Bute there are two shortages in this (generally very good) idea.2a) In Nokia Camera the "Photo camera" icon is moving left just under the finger while being dragged, while in K920 Camera app "Photo camera" icon is moving only after dragging is finished & the finger is moved away from the screen. Such a behaviour looks a little bit unnatural.2b) In Nokia Camera I can show the single curve for the tuning of a single parameter by pressing a corresponding button on the center of the top side of the screen. The K920 Camera app doesn't have such an ability at all (or I failed to find it).This video illustrates the problem.3) It would be very good to add the next options: disable shutter sound, change photo resolution (5M, 8M, 16M) and aspect ratio (16:9, 4:3).4) The Zoom function in video recording mode works like simple pixelization, not zoom. Neither Lumia 1520, nor HTC One X (my other phones) doesn't zoom in video mode like K920. The two videos - about Lumia 1520 zoom & K920 zoom illustrate the problem. This is the more so strange, that in photo mode K920 zoom is apparently better than the Lumia 1520 one. Sound1) It would be great to realize step-by-step volume increasing for incoming calls. Thank you.

Hi monocats,
Yes, I have expirienced quite the same camera issues as you, but only 5 or 6 times of more than 200 photos, so made little for this issue.
Link to image
Link to image
I'm a newbie in photography, but noticed, that slightest chage in camera position result in disappearing such artefacts as on the photos above. So it can be result of a light sources mutual position and some camera hardware aspects.
Moderator note: Large image/s converted to link/s About Posting Pictures In The Forums

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

Is there any way to see graphs and charts of how much code was covered during Unit Tests in OBPM 10GR3 from the CUnit and PUnit tests?
We use Clover Reports in Java Projects.
Any such tool for OBPM 10GR3 projects?

Here are some more
Triggers and DB links are not available in Oracle Explorer - it would be great to have them in there - I found triggers under tables - but I would much prefer them to be broken out under their own node rather than nested under table
I think others have mentioned this but when you query a table (Retrieve Data) - it would be great to be able to specify a default number of records to retrieve - the 30 second timeout is great - but more control would be nice - also a way to control the timeout would be nice as well
I noticed that I get different behavior on the date format when I retrieve data (by selecting the option from the table menu when I right click on a table) versus getting the same data through the query window - why isn't it consistent?
Also - with Intellisense - can you make the icons different for the type of objects that the things represent (like tables versus views versus functions)
I noticed that I couldn't get dbms_output to show up with Intellisense - I had filtered out of Oracle Explorer all the System objects - does that somehow affect Intellisense as well? I know that the account I am using has access to those packages.
Also - more control over collapsible regions would be nice - I love that feature of VS - but for ODT it seems to only work at the procedure level (not configurable with some kind of directive etc...)

Unit Testing and APEX Global Variables

We've recently started to unit test our database level PL/SQL business logic.
As such we have a need to be able to simulate or provide output from PL/SQL APEX components in order to facilitate testing of these components.
Some of the most obvious portions that need simulation are:
1. The existence of a session
2. The current application ID
3. The current page ID.
We currently handle requirement #1 by using apex_040100.wwv_flow_session.create_new
We handle 2 and 3 using the apex_application.g_flow_id and g_flow_step_id global variables.
I'm just wondering, how safe is it for us to use wwv_flow_session.create_new to simulate the creation of a session at testing time for those things which need a session?
I've also noticed that there are apex_application.get_application_id and apex_application.get_page_id functions whose output is not tied to the global variables (at least in our current version).
Is it safe for us to expect that we can set these global variables for use in testing or is apex moving to get_application_id and get_page_id functions away from global variables?
Will there be corresponding set_application_id and set_page_id functions in the future?
Sorry for the question bomb. Thanks for any help.

My first question would be why do you need to establish a session to test your PL/SQL?
wwv_flow_session is a package internal to APEX, and you should probably leave it be.
The get_application_id procedure you refer to is in apex_application_install, which is used for scripting installation of applications - not get/set of page ID like you're describing.
If you're uncomfortable using apex_application.g_flow_id, you can use v('APP_ID') or preferably pass the app_id/page_id as parameters to your procedures.
Your question seems to have a few unknowns, so that's the best I can describe.
Scott

Unit testing and Issue on ODS

Hi every one,
I was asked to do Unit testing on all the objects I created which includes data loading, checking the structure.....etc...If any one has any template for Unit testing pls forward it to me [email protected].....
My ods is designed with out checking "Activate ODS data immeaditely".....and we r not using process chains here...
while testing data loads when ever we send data data to that ODS how do u activate it thru jobs automatically????
if we give Job selection it may not work out right, cos we don't know when we load data....so can I make use of events so that when ever data comes to ODS I need to activate it and it has to push that data to other ODS...can anyone throw some light on the events and what even to use for automatic activation....
If any one has any template pls forward it to the above ID
Thanks in advance

BW
Doing unit test is simple. Just document what ever the steps you follow while loading your ODS. You could follow these steps
1 . Check the functionality of your Infosource whether it is full or Delta Take a screen shot.
2.   Check Delta Load Functionality if you have any Delta extractors.
4     . Schedule the Info Package
5     Go to Manage Data targets and see whether ODS got loaded successfully or not.
6     Check if it is activated or Not. In your case it will automatically gets activated since you selected automatic activation.
Dont forget to take screen shots of each Process
Hope this helps
Thanks
Sat

Unit Testing and Oracle Sessions

We have an issue regarding Oracle session and SQL Developer Unit Testing.
Every time we run a Unit Test in SQLDeveloper a new Oracle session is created. When closing that Unit Test, the session, however, is not disconnected.
And the only way to close that "Unit Test" session is to close SQLDeveloper.
This is causing problems with the no. of sessions available to developers.
Any help would be much appreciated.
Subboss

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

Similar Messages

Maybe you are looking for