HomeUser GuideMiscellaneousKeeping Separate Text Fields for Steps vs Single Field

13.6. Keeping Separate Text Fields for Steps vs Single Field

Because of popular demand, with the launch of version 1.14.1 on June 25th 2016, we have added a new feature that takes defining test case steps, their expected results and their execution to a detailed level. 

While adding a new project on your Test Collab instance you will get option to enable "Separate text fields for steps and expected result".

When separate text fields for steps is not enabled then you enter all the steps in a single text field one after the other by separating them using two consecutive new line characters, and to provide expected results you again have single box. 

If you opt to enable separate text fields for steps and expected results then at the time of creating test cases you will get an interface that would allow you to define steps in separate text fields and also provide expected result for each step individually. 

Let's look at how execution window looks when you have not opted to use separate text field for steps and expected results : 

If you notice steps are clubbed which is fine for majority of projects or testing styles. However some projects might require more granular control over execution steps, to keep a track at which step a particular case failed.

Let's look at how this new feature gives you more flexibility:

Now there a pros and cons to both the approaches and you should choose the style that suits more to your team. If you don't know - just go with the flow and leave this setting.

Advantages of using Separate Steps:

1. Granular control over execution so your team knows exactly where the case was failed.

2. Comment on each step separately.

Disadvantages of using Separate Steps:

1. Requires more time in writing test cases.

2. Requires more time while executing test cases.

 

This page was: Helpful | Not Helpful
Test Case Management
Test Collab Support
Product Tour