on 02-21-2007 6:42 AM
hai
can anyone let me know the process of doing unit testing and integration testing in sd , i know that unit testing will be done in the dev server and integ in qa server . kindly provide me the details along with practical scenario
urgent replies will be appreciated
thanks
kishore
Dear Kishore,
I hope my document sent through mail helps you. Please do not forget to award points since it is a practical doc.
Rajib
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi!
I am a new member to this forum. I have 3 yrs of exp in space selling and 3yrs in BPO. I am in ambiguity for SD or CRM. Pl advise me on this. Thanks in advance.
regards
mahend
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can anyone plz forward those doc to afrozemujtaba@gmail.com
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Kishore,
Sorry to put it this way but I think you forget to put points for my efforts. Please award me suitable points.
Regards,
Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you srini and rajib
my mail id is kdhanekula@gmail.com
regards
kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
Unit Testing is carried out to test the process pertaining to a single module.
Integration Testing is carried out to test the entire scenario especially how one module correlates with the other.
for example in SD -
Testing if Inquiry, Quotation, Sales Order, Delivery Documents, Billing Documents is Unit Testing,
Testing if Requirements are transferred, Accounting/ Controlling documents are generated, G/L account postings have been done etc fall under Integration Testing.
Regards
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please furnish your e-mail id for attaching doc.
Rajib
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
Give me your mail Id i will send you some notes
Regards
Srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
One scenario could be for any output message being sent to external party (eg..contract manufacturer)..
Functional unit testing would be to ensure the output type is being determined correctly in the SD document
And integration testing would be that the output message is being received by the external party.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Kishore,
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
Please award points if found useful.
Regards,
Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.