BHARAT TEST SUITE by Raju Bros Softech Pvt ltd

Application example

From test identity
to report evidence.

Explore the existing public example report to understand how a unit summary, measured values and saved vision evidence fit together.

View the example PDF
/01

What this example demonstrates

Reviewed 15 October 2026 · Raju Bros Softech Pvt ltd

Example, with demonstration values. This document is based on an actual test report. Display branding and model labels were updated; cycle time and matching start/completion timestamps use demonstration values. Measured values, step results and images were preserved. It is a report walkthrough, not a throughput benchmark, customer endorsement or proof of a production improvement.

The report shows a DEMO MODEL unit, one fixture position and a named test sequence. Its summary contains 90 steps, 90 PASS results and zero failed steps. The displayed cycle time of 01:56.375 is a demonstration value; it must not be used to estimate your line capacity.

Open the 29-page example test report (PDF)

Example test report · Summary Demonstration values
Existing public example · Page 1 of 29. Model names, cycle time and matching start/completion timestamps use demonstration values; measured values, step results and images are preserved.
/02

Read the report in three passes

  1. Start with identity and outcome

    On page 1, check the unit barcode, model, logical model/sequence, fixture, result and total step counts. This establishes which test attempt the document describes.

  2. Inspect visual evidence

    Page 2 presents original and processed camera images for Step 39 alongside segment validation. Page 3 continues with chromaticity information. Relate each image to its named step and recorded result.

  3. Review individual measurements

    The step-detail section begins on page 26. Compare the actual value with the configured minimum and maximum, read the unit and check the row result. Action-only rows can show execution status instead of a numeric measurement.

Example observation How to interpret it
Step 32 on page 26: 5.2500 A minimum, 5.4457 A actual, 6.4100 A maximum, PASS. The saved current value lies inside that row’s configured range. This describes one saved result; it is not an accuracy specification or process-capability study.
Step 39 contains image evidence and segment results. A saved image gives review context for the configured inspection. Camera calibration, lighting and the meaning of each limit must be established for the real application.
Summary: 90 steps passed. The configured report records a passing attempt. One successful report does not establish long-run yield, repeatability or throughput.
/03

Connect an image to its test step

The original and processed images let a reviewer see the captured scene and the marked inspection regions. The report’s segment table supplies the numeric context. Use them together instead of judging a result from the green overlays alone.

Vision evidence · Step 39 From the example report
Existing public image extracted from the example report. Segment overlays illustrate the saved evidence; inspection suitability requires validation for the intended product and camera setup.

Image evidence is available when the configured workflow captures it. The report layout and content depend on the selected test, enabled report steps and available evidence; the appropriate feature licence and hardware are also required.

Reporting and traceability capabilities ↗ Device compatibility ↗
/04

Build evidence for your own application

Use this document to decide what your acceptance report must contain. Then collect results on the intended product and station, with your approved limits and representative conditions.

  • Define required identifiers, measurements, units, limits, images and final-result fields before the demonstration.
  • Record the instrument, fixture, camera, firmware, driver and application configuration used for evaluation.
  • Run representative passing and failing conditions, including a controlled communication failure and stop/recovery check.
  • Review repeated runs and actual timing against your baseline; retain the complete conditions and limitations with any measured claim.
  • Confirm that the expected PDF, CSV or TXT records are created and can be retrieved by unit identity.
Plan an application demonstration ↗ Explore production testing ↗
/05

Example report questions

Is 01:56.375 a guaranteed cycle time?

No. It is a demonstration value in this public example, with matching demonstration timestamps. Establish actual timing using your sequence, instruments, fixture, reporting and operator workflow.

Were the measured values and images fabricated for this page?

The existing public example is based on an actual report. Its preparation checks preserve measured values, step results and image payloads while changing display labels and demonstration timing. This page reuses those public assets without changing them.

Does a PASS report prove compliance with a product standard?

A report shows the outcome against the configured test steps and limits. Any standards claim needs the applicable test method, calibrated equipment, validated configuration and required independent evidence.

Can I use the example limits for my product?

Treat them only as an explanation of the report. Set limits from your product specification and approved test procedure, then validate them on the intended station.

Need help with your test station?

Share your instruments, intended workflow and the question you need to resolve.

Discuss your station

BHARAT TEST SUITE · Application screen