Skip to main content
CodeMeg8-Gravel
8-Gravel
Apr 7, 2025 2:18 PM UTC

Test Management: Creating and Executing Test Cases with Parameters | Test Library Overview

  • Nov 2, 2026 3:15 PM UTC
  • 0 replies
  • 562 views
  • Translate All

In this Codebeamer video, we'll guide you through the process of creating test cases, assigning parameters, and executing them online. Along the way, we'll also provide an in-depth explanation of the test library and its features. Whether you're a beginner or an experienced tester, this tutorial will help you streamline your testing process and improve efficiency. Don't forget to like, comment, and subscribe for more technical tutorials!

 

 

Watch Guide

 

Overview

This 7-minute Codebeamer how-to video shows how to create a test case in the Test Case tracker, link it to the requirement it verifies, add pre-actions, post-actions, test parameters and test steps, then execute it as a test run. A cruise control example uses one velocity parameter to run the same test case at 70, 80 and 90 km/h, and the video ends by deriving a test case directly from a system requirement. It is aimed at testers and engineers who are new to test management in Codebeamer.

 

Chapters

This video has chapters, available from the YouTube player menu.

  • 0:00 to 0:26: Test case creation overview
  • 0:26 to 1:22: Defining test case details
  • 1:22 to 2:13: Assigning test parameters
  • 2:13 to 4:05: Configuring test steps
  • 4:05 to 6:35: Executing the test run
  • 6:35 to 7:39: Deriving tests from requirements

 

Key Takeaways

  • In Codebeamer, the Verifies field of a test case links it to the requirement it tests, for example a system requirement.
  • Test parameters are selected from the Test Parameters subsection of a test case. The parameter source can be uploaded to wiki pages or, as in the video, an Excel file can be uploaded to the Document Manager.
  • In the parameter Excel file, the referenced expression goes in the first row and its values go underneath it in the same column. Add more parameters in the following columns.
  • Referencing a parameter such as velocity in a test step lets one test case run for several values (70, 80 and 90 km/h in the demo) instead of creating three separate test cases.
  • Test steps can include pictures, a Critical checkbox, and an expected result for each action.
  • A test run is generated from the test case with the New Test Run icon and started with the Run icon. The runner shows pre-actions, test steps, post-actions, a completion tracker, a time tracker and an Actual Result field.
  • If any step fails, the overall test run result is a failure. Charts and statistics in the results overview still show which parts of the test passed.

 

How do I create a test case in Codebeamer?

Create a test case from the Test Case tracker, then open it for editing to define what it verifies and what must happen before and after the test. The pre-action and post-action fields support the usual Codebeamer text editing, file upload and linking options.

  1. Open the Test Case tracker: Navigate to the project's test case tracker and create a new test case.
  2. Open the editor: Open the new test case and click the pencil icon in the top left corner to edit it.
  3. Set the Verifies field: Select the requirement the test case verifies (a system requirement in the example) and add it.
  4. Define the pre-action: Describe what has to take place before the testing procedure begins.
  5. Define the post-action: Describe what has to take place after the testing procedure is done.

Watch: 0:26 to 1:22 (creating the test case and filling in the Verifies, pre-action and post-action fields)

 

How do I add test parameters from an Excel file to a Codebeamer test case?

Add parameters by selecting a parameter source from the Test Parameters subsection of the Codebeamer test case. The source can be uploaded to wiki pages or, as in the video, an Excel file can be uploaded to the Document Manager. In the Excel file, write the referenced expression in the first row and list its values underneath it in the same column; add more parameters in the next columns.

  1. Prepare the parameter file: Put each parameter name in the first row and its values below it, one column per parameter.
  2. Upload the file: Upload it to the Document Manager (or put the parameters on a wiki page).
  3. Select the parameters: In the Test Parameters subsection of the test case, choose your parameter file from the drop-down list. The values in the file can now be referenced in the test case.

Creating, uploading and managing parameter templates and documents is covered in a separate video.

Watch: 1:22 to 2:13 (the example parameter Excel file and selecting it from the drop-down list)

 

How do I add test steps that use parameters in Codebeamer?

Add test steps to the Codebeamer test case and reference a parameter inside a step, so the same test case runs once for each parameter value. In the demo, a step references the velocity parameter, so there is no need to build three test cases for three speeds. Each step can also hold pictures, a Critical checkbox and an expected result.

  1. Add the first step: The example step turns on the cruise control, with a picture added to illustrate it.
  2. Reference a parameter: In the second step, set up a reference to velocity, a value contained in the uploaded parameter file.
  3. Add a final step and expected results: Add the last step, then enter an expected result next to each action.
  4. Save the test case: Save the test case when the steps are complete.

The test case library in the bottom right corner of the editor helps reduce redundancy further; it is covered in a separate video.

Watch: 2:13 to 4:05 (building the three test steps, adding a picture, the parameter reference, the Critical checkbox and expected results)

 

How do I run a parameterized test case in Codebeamer?

Run a Codebeamer test case by generating a test run from it with the New Test Run icon, saving the run, and starting it with the Run icon in the top left corner. The built-in runner lists the pre-actions, test steps and post-actions, and includes a completion tracker, a time tracker and an Actual Result field for recording results. Because the test case uses a parameter, the runner repeats the steps for each value: 70 km/h, then 80 km/h, then 90 km/h in the demo.

  1. Create the test run: Click the New Test Run icon on the test case and save the run (the details can be left as they are).
  2. Start the run: Click the Run icon in the top left corner.
  3. Record each step: Enter actual results and pass or fail each step.
  4. Close the round: Add comments and notes in the pop-up window that appears when the round is finished, then continue with the next parameter value.
  5. Review the results: Save the run to see the results overview.

When a step fails, the closing pop-up window also offers to report a bug immediately (bug reporting is covered in a separate video). If any step fails, the overall result of the run is a failure, but the charts and statistics show which parts of the test were successful.

Watch: 4:05 to 6:35 (the test runner, passing the 70 and 80 km/h rounds, failing a step at 90 km/h and the results overview with charts)

 

How do I derive a test case from a requirement in Codebeamer?

Derive a test case from a requirement by clicking the plus icon next to the requirement in its tracker and choosing a test case. The same test case editor opens in a pop-up window, with the only difference that the Verifies field is already filled in. After saving, the requirement's downstream references section lists every test case that verifies it.

  1. Open the requirement: Go to the system requirements tracker and select the requirement (Cruise control in the demo).
  2. Derive a test case: Click the plus icon next to the item and choose a test case.
  3. Edit and save: Change the name and save; the Verifies field is pre-filled.
  4. Check traceability: In the details of the requirement, the downstream references section in the bottom right now shows both test cases.

Watch: 6:35 to 7:39 (deriving the test case from the Cruise control requirement and the downstream references section)

 

Frequently Asked Questions

 

Q: Do I need a separate Codebeamer test case for each input value?

A: No. Reference a test parameter in the test steps and the same test case runs once for each value in the parameter source. In the video, one test case covers 70, 80 and 90 km/h. (shown at 2:47)

 

Q: Why does my Codebeamer test run show a failed result when most steps passed?

A: If any step in the run fails, the overall result is a failure. The charts and statistics in the results overview show which parts of the test passed. (shown at 6:16)

 

Q: Can I report a bug directly from a failed test step in Codebeamer?

A: Yes. When a step has failed, the pop-up window at the end of the round includes an option to report a bug instantly. (shown at 6:01)

 

Q: What is different when a test case is derived from a requirement?

A: The editor opens in a pop-up window and the Verifies field is already filled in with the requirement. Everything else works the same way as creating the test case in the Test Case tracker. (shown at 7:06)

 

Links & Resources

Terms & ConditionsAccessibility statement