In this article we are going to cover the main entity around which the entire test case management tool is designed and working.

When an authorized user has opted to add a test case, then a form to enter new test case information will be shown.

 

User can provide information like 

  • Association of the new case with a pre-existing test suite
  • Title of the case which should be brief but self explanatory
  • Priority of the test case is to be selected from a set of options like - Low,Normal and High
  • Description, though not mandatory but is one of the prime sources of information to tester, the description can be details about test case or any pre condition which may be some kind of settings or scenario that should exist prior to a test has initiated
  • Steps, these are the most important set of one or more instructions to execute the tests, arranged in a logical sequenceIn the editor provided for steps, he will have option to add the defined steps that are included under the test case, 
  • For each step, user should be clear in defining the part of the procedure that step is expected to be used for, 
  • To separate 2 steps user should provide a gap of 1 line by hitting Return (Enter) key twice, 
  • To provide the properties (format) for text being used for each step user will have set of icons associated with the text editor. 
  • When Markdown editor type is being used then the steps that have been defined as reusable steps can be easily imported for the test case by using the given icon. (user can also define new set of reusable steps, if they don't exist by using the same icon)
  • Once the user opts to import reusable steps, a window will popup to let the user select the reusable step to be added, if no set exists then user can add new (if he is authorized to do so) 
  • Followed by steps, will be the expected result (outcome) of the test procedure
  • Test case can be linked with one or more requirements raised in the "development project"For this a comma separated list of Ids of the requirements that need to be linked with the test case should be provided 
  • Custom fields that have been defined under the project that are to be used for test cases will be available for data entry / selection
  • Skip conditions, these will be available only when custom fields of type "Option box" and "Multiple Choice Option box" have been defined under the selected project that are to be used for test execution; skip conditions help the tester to avoid execution of unnecessary steps for a specific environment, and to avoid guess work
  • For this user can select a custom field to be used in condition and select the value for it to drive the condition
  • If required, user may upload file(s) to provide more relevant/detailed information to the tester
  • A number of tags can also be associated with a test case
  • For tags, user has an option of either selecting from pre defined tags or to define and add a new one

All the information collectively helps the tester to map out, how a part of a process should behave when executed.

Here Suite, Title, and Priority of test case are mandatory fields.

If at the time of adding the project "Separate text fields for steps and expected results" is enabled, then at the time of defining the test cases, instead of a single text field for all steps, separate text fields will be made available for entering individual test steps and their respective expected results, as shown in image below.

User has an option to add as many steps as he wants by clicking Add more steps link provided. User can also delete the steps using the Cross button. 

Reordering Steps

With version 1.16 of Test Collab comes the feature of ordering the steps. One can now drag and drop a step along with its expected result from one position to the other in steps list. 

 

Please note that the feature of reordering of steps would not work when HTML Editor is used as Editor Type for test case steps, expected result and description.

 

 

 

Did this answer your question?