The RiDP compatibility test process enables developers to acquire production signatures for their solutions. Testing of the solution will focus on ensuring that the integration and implementation of the tested solution does not adversely affect the features and functions of the Ricoh MFP’s that support the Ricoh Platforms. Compatibility testing result is valid ONLY for TWO years. Maintenance signature cannot be provided for a solution which the latest compatibility testing has been completed two years ago.
Please note: Primary responsibility is placed on the developer to test their own products; all submissions must be accompanied by a written certification that the tests have been performed as described.
Compatibility Testing Document Sets
Disclaimer: The information below is still in review. Please be sure to request any clarification if you are unsure or confused with any of the information provided below.
Below are the steps that outline the Compatibility Testing process:
Note: For steps 1 - 4 you’ll be able to move on if you receive a pass, if you receive a fail, your Compatibility Testing request will be denied and/or paused. Each step will provide information on pass/fail cases. Our goal was to document the most common examples, however, some situations may not be documented.
Step 1: Complete the Compatibility Testing Webform
Compatibility and QA testing begins with the completion of the Ricoh Compatibility Testing webform which members should fill out and answer ALL fields. If there are any questions, comments or concerns, its important that you open an incident to clarify and/or request assistance. The webform allows the ability to “Save” your submission as a draft, in the event you don't have all of the required information at your disposal. This capability allows you to complete your submission process over several days if necessary as you collect the materials required.
Pass: When the form has been completed correctly, the form may be submitted and then proceed to step 2. The webform is automated, and an incident will be created on your behalf. Be sure to read the webform thoroughly, as once the webform has been submitted as final, it may not be edited.
Fail: Once the form is filled out and submitted, the Support Engineer assigned to your incident will review the submission. If anything is missing or incorrectly documented, you’ll be asked to re-submit the webform and/or provide clarification information. Should a redo of the webform be required, the initial incident will be closed and the RiDP Support Staff will wait until a newly submitted webform is processed, before proceeding.
Step 2: VMware Submission Process
Following completion of the Compatibility Testing webform, a new incident will be opened on your behalf in our Support System. A RiDP Support engineer will be assigned to your incident and work with you to schedule time to allow you or someone in your team to install, configure and TEST all server side components which are required for your solution to function. Please review the following FAQ “What is the VMware submission process?” for more information on VMware submission.
Pass: Once all of the software is installed and configured by you or a member of your team.
Fail: If at any point you are not able to install or configure the server.
Step 3: PreTest
Once the VMware is setup on RiDPs servers, the RiDP Support Engineer handling your Support Incident will proceed with the Pretest. The purpose of Pretesting is to verify and analyze your solution at a high level. The main functionality of your overall solution will be tested. In some cases, more test cases will be performed in order to ensure the submission is ready for RiDP testing. Note: Four hours of pre-testing is at no charge, hourly fee applied for all hours beyond to completion of pre-testing. If solution fails pre-testing and no charge hours have been utilized, resubmission hourly charges begin when pre-testing begins.
Pass: If the Support engineer is able to successfully run a high level test on the main functionality of your solution. Resolution of deferred issues from previous test submissions will be confirmed before proceeding.
Fail: Various reasons will cause a failure in this step, here are some of the common issues: if the solution experiences functionality issues on the common functions, solution does not have a RXOP installer, deferred issues are not fixed, documentation is not substantial for RiDP and others.
Step 4: Formal Test
After Pretesting is completed and passed, RiDP will start creating test cases based on the information provided in the Compatibility Testing webform “Compatibility Testing Services Requested” section.
Pass: Solution is found to not have any major defects/issues. Minor defects/issues will be allowed to be deferred. (Following evaluation and review by RiDP staff)
Fail: If any major issues are discovered Ricoh will use their discretion to determine if the issue results in a mandatory failing grade, or if the issue is judged to be minor, Ricoh will exercise the option to defer to the next test cycle. If there are too many minor defects found within the solution, this could also lead to a failing grade. During the formal testing phase it’s important to have engineering staff available so that they may analyze and fix any small issues that would cause a failure. Ricoh reserves the right to fail a solution outright if issues are not resolved expeditiously.
Step 5: Release - Compatibility Testing Report, Production Signatures (Application Zip file, Access Token)
Once you have passed Compatibility Testing, you’ll receive your Production signature or Production level Access Token. You’ll also receive a Compatibility Testing Report and invoice for test service utilized.
Fee Schedule
Fee Schedule 2022 - RiDP Fee Schedule Document