Welcome

Welcome to HandsonERP.com

This site provides video based training of Oracle Financials.
Learn concepts and functionality in a step by step manner.

Login

HandsonERP - Oracle E-Business Suite Training
Welcome, Guest
Please Login or Register.    Lost Password?
Please post inquiries related to lessons content here. All questions and inquiries related to the website should be submitted directly using Contact form in the top menu.
Go to bottom Post Reply Favoured: 0
TOPIC: Re:Test Script & Documentation.
#2212
liben (User)
Expert Boarder
Posts: 97
graphgraph
User Offline Click here to see the profile of this user
Test Script & Documentation. 12 Years, 7 Months ago  
Hello Hasan

What do we have to do if
A client asked us to prepare A Test Script & Documentation for an existing modules?

Thanks Always.
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#2213
dhayaz (User)
Fresh Boarder
Posts: 1
graphgraph
User Offline Click here to see the profile of this user
Re:Test Script & Documentation. 12 Years, 7 Months ago  
Hi Hassan,
My company is going to upgrade from 11i to R12.Please advice that what are various kinds of testing that we need to perform in the role of a techno functional consultant.
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#2224
handsonerp (Admin)
Admin
Posts: 1989
graph
User Offline Click here to see the profile of this user
Re:Test Script & Documentation. 12 Years, 7 Months ago  
Liben,
Your client has asked you to prepare test script and documentation? Test script is one thing and documentation is another. Question is what kind of documentation?
For the test script:
You would first which functionality client wants to test?
Lets say if the client is using Payables module then
1) Would they like to test all the functinality they are using (Most likely this would be the choice).
2) Would they like to test all AP functionality irrepective if they are using it or not.
3) Would they like to test specific area like Payment?
Once it is cleared what the client wants to test you would prepare a list of functional areas to be tested like
1) Invoice Entry
2) Invoice Validation
3) Invoice Approval
4) Payment via Check
etc
For each functional area you would list down Business processes that you could use to achieve the functional objective.
For example for function area 4 you would list
1) Pay the invoice through Invoice Workbench
2) Pay the invoice from Payment window
For each business process you would list down steps and expected results. Then you will conduct the test and list down the actual results.
In short it is a common sense thing. Use any format. But the testing must cover all areas that needs to be tested.
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#2225
handsonerp (Admin)
Admin
Posts: 1989
graph
User Offline Click here to see the profile of this user
Re:Test Script & Documentation. 12 Years, 7 Months ago  
Dhayaz,
I am assuming you are talking about testing that would perform after the upgrade.
Before the upgrade you will create a business procedure document showing users how to perform day to day tasks the R12 way. It would be different than the same document that they had for 11i. The same document will become the basis for their training.
Based on your business procedure document you will create a test script. You would want to find out if all functional areas that your business users will use are working as expected. This testing is done by functional consultants.
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop