How to Capture Test Results for Multiple Samples in Jama Connect®

Published Date: November 3, 2026
Audience: Everyone
Products and Versions Covered:

All Jama Connect® version(s)

Summary

Jama Connect® does not allow users to add multiple instances of the same test case to a single test cycle. This can create challenges when a test procedure requires testing of multiple samples using the same procedure and each samples result(s) must be recorded separately.

The recommended approach is to capture results for all samples within a single test run, using repeated test steps or a structured data table in a custom field.

Resolution

Recommended Approach: Capture Multiple Samples in a Single Test Run

When multiple samples follow the same test procedure, capture the results for all samples within a single test run.

This approach keeps the test procedure and its associated sample results together, making it easier to review and evaluate the complete testing activity.

Repeat test steps for each sample. Structure the test case to include the required steps for each sample. For example, after defining the test steps 1–5, add another step instructing the tester to repeat those steps for samples 2–10 and record the results for each sample.
Use a structured data table. Add a table to the Actual Results field or configure a dedicated sample data capture field. An editor template can prepopulate the table with the required columns, such as sample identifier, measured results, expected values, pass/fail determination, and test date. Testers can add additional rows to the data capture table as needed.

For tests conducted over multiple days, ensure that the execution date and time for each sample are captured when required by the testing protocol.

This approach is generally preferred when all samples follow the same procedure, share the same test configuration, and can be documented as one overall test execution.

Alternative Approach: Use Separate Test Cycles for Each Sample

When samples require independent execution records, create separate test cycles within the same test plan. Each test cycle generates its own test run for the associated test case.

Consider this approach when:

Testing occurs over multiple days: Each sample or testing session requires an independent execution record or review signature.
Different testers perform the work: Individual samples or groups of samples need to be assigned to different users.
Testing requires different configurations: Samples are tested under different configurations or conditions that should be documented separately at the test cycle level.

To implement this approach:

Create a test plan containing the applicable test case.
Create a separate test cycle for each sample or distinct testing configuration.
Include the test case in each cycle to generate an independent test run.
Record the sample identifier, applicable configuration, and execution results in each corresponding test run.

Important note regarding automatically calculated test case status:

When using multiple test cycles to represent individual samples, do not rely on the automatically calculated Test Case Status field to determine the overall result of all samples for the given test case.

For a test case associated with a single active test plan, Jama Connect calculates the test case status using the most recent associated test run. It does not evaluate all sample-specific test runs collectively to determine whether every sample passed.

For example, if five samples are tested in separate cycles and the most recent test run passes, the test case may display a Passed status even if an earlier sample failed.

Because the calculated status does not accurately represent the collective results of replicate testing, the Test Case Status field should be ignored or hidden from view when using this approach. An organization administrator can hide this system-managed field for the applicable test case item type.

Review the individual test runs to determine the results of each sample and the overall testing outcome.

Additional Considerations

The appropriate approach depends on the testing protocol, the number of samples, and the level of execution detail required.

For complex testing scenarios, including large sample quantities, automated testing, or the use of test parameters, additional evaluation may be necessary to determine the most appropriate configuration.

For further guidance, contact your Jama Software® consultant or request a test management consultation to discuss your specific testing requirements.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to