Manual Test Scripts: Execution Steps vs. Reporting Steps
Hi All,
I'm trying to figure out the differences between those 2 types of steps in Manual Test Scripts (Execution and Reporting).
I get what's the idea behind it: actions and verifications points.
But, does RQM have any functionality that uses that distinction?
A report that get results from one and not the other, for example?
Or the difference is only conceptual?
If anybody is using those types for a specific reason, I would like to know.
Thanks
I'm trying to figure out the differences between those 2 types of steps in Manual Test Scripts (Execution and Reporting).
I get what's the idea behind it: actions and verifications points.
But, does RQM have any functionality that uses that distinction?
A report that get results from one and not the other, for example?
Or the difference is only conceptual?
If anybody is using those types for a specific reason, I would like to know.
Thanks
2 answers
-
Execution steps
(
) tell testers which actions to perform when they run the script. For example, "Start the application." represents an execution step.
-
Reporting steps (
) are higher-level checkpoints. Reporting steps might summarize the result of several execution steps. For example, a reporting step might ask, "Were you able to log in?"
-
Information steps(
) enable testers to add notes, cautions, setup instructions, or delays between steps during test case execution. For example, “Set Voltage to 5V and temperature to 10ºC.” is an information step.
-- Steve