1. Data Management
  2. RapidValue
  3. Flows

Test
Activity Flow

As a tester, use test runs to do the test and report the results.

For each test case in the test run, you can:

  • Define the status.
  • Enter a conclusion.
  • Add requirements.

Tester Tester Enter test results for test case Enter test results for test case Follow the test cases to do the actual test. For each test case done, enter your conclusion. Procedure 1. Click My test runs. 2. Click the Scheduled tab. 3. In the list, mark the selected row. 4. Click Status. 5. Click Started. 6. Click the Started tab. 7. In the list, mark the selected row. 8. Click Edit. 9. Click the Procedure tab. 10. In the list, mark the selected row. 11. In the Test case conclusion field, type a value. Create requirement for test case Create requirement for test case If you found a defect or any other issue during the test, you can add a requirement to the test case to get it solved. Procedure 1. Click My test runs. 2. Click the Started tab. 3. In the list, find and select the desired record. 4. Click Edit. 5. Click the Procedure tab. 6. In the list, mark the selected row. 7. Click Add requirement. 8. Click Edit. 9. Close the page. Start Start Change test case status Change test case status If you have completed a test case, and if required also added requirements, you can assign the appropriate status to the test case. Procedure 1. Click My test runs. 2. Click the Started tab. 3. In the list, mark the selected row. 4. Click Edit. 5. Click the Procedure tab. 6. In the list, find and select the desired record. 7. To change the test case status, click one of these buttons: Reset, Pass, Fail, or Skip. 8. Close the page. Notes If you change a test case status, automatically the next test case is selected. Change test run status Change test run status The test run status is automatically updated based on the test case statuses. However, you can change the test run status manually. You can do so, for example, if the test run has no test cases or if you want to overrule the automatically defined test run status. To test runs, you can assign these statuses: Created: The test run is created but not yet ready to be done.Scheduled: The test run is ready to be started.Started: The test run is started.Failed: Errors are found during the test run.Passed: The test run was completed successfully.Skipped: The test run is not done. Procedure 1. Click My test runs. 2. Click the Failed tab or Passed tab. 3. Click Status. 4. Select the required status. Publish test report Publish test report For each test run, you can publish a document with detailed information on what is tested and what are the test results for the related test suite and its test cases. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. Procedure 1. Click Business process testing. 2. Click the Test runs tab. 3. In the list, find and select the desired record. 4. Click Publish. 5. Click Test report. 6. On the Publish Test report document dialog, define the required settings and click OK. Notes On the Publish test report document dialog, you can define these settings:Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.Include version number - If this check box is selected, the version number of each element is added to the document.Include change history - If this check box is selected, the change history of each element is added to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published. End End Did you find  an issue  to be solved? Did you find  an issue  to be solved? Next test case  to be done? Next test case  to be done? Override  test run status? Override  test run status? Yes No Yes No Yes No

Activities

Name Responsible Description

Enter test results for test case

Tester

 		Follow the test cases to do the actual test. For each test case done, enter your conclusion.

Create requirement for test case

Tester

 		If you found a defect or any other issue during the test, you can add a requirement to the test case to get it solved.

Change test case status

Tester

If you have completed a test case, and if required also added requirements, you can assign the appropriate status to the test case.

Change test run status

Tester

The test run status is automatically updated based on the test case statuses. However, you can change the test run status manually. You can do so, for example, if the test run has no test cases or if you want to overrule the automatically defined test run status.

To test runs, you can assign these statuses:

  • Created: The test run is created but not yet ready to be done.
  • Scheduled: The test run is ready to be started.
  • Started: The test run is started.
  • Failed: Errors are found during the test run.
  • Passed: The test run was completed successfully.
  • Skipped: The test run is not done.

Publish test report

Tester

 		For each test run, you can publish a document with detailed information on what is tested and what are the test results for the related test suite and its test cases.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Activities

Name Responsible Description

Enter test results for test case

Tester

 		Follow the test cases to do the actual test. For each test case done, enter your conclusion.

Create requirement for test case

Tester

 		If you found a defect or any other issue during the test, you can add a requirement to the test case to get it solved.

Change test case status

Tester

If you have completed a test case, and if required also added requirements, you can assign the appropriate status to the test case.

Change test run status

Tester

The test run status is automatically updated based on the test case statuses. However, you can change the test run status manually. You can do so, for example, if the test run has no test cases or if you want to overrule the automatically defined test run status.

To test runs, you can assign these statuses:

  • Created: The test run is created but not yet ready to be done.
  • Scheduled: The test run is ready to be started.
  • Started: The test run is started.
  • Failed: Errors are found during the test run.
  • Passed: The test run was completed successfully.
  • Skipped: The test run is not done.

Publish test report

Tester

 		For each test run, you can publish a document with detailed information on what is tested and what are the test results for the related test suite and its test cases.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.
Related to Notes

Test

 		 

Provide feedback