Troubleshooting: Spelling and Punctuation Errors

A common source of test case failures is spelling and punctuation errors. Additionally, whitespaces need to be correct.

Solution: Spelling Errors

The report for a failed test case with spelling errors appears similar to the following:

In the intaQt Studio log window, it looks similar:

The report shows in which part of the Feature File to look. The problem in the example above is not the angle brackets, but the content within them: callingPart instead of callingParty has been used in the test case:

Test Case Example

Feature: SMS
  Scenario: SMS_originatedBasicSMS
    Given an Android phone as A
    And an Android phone as B
      And A composes a short message
      And A types "Hello, world"
      And within 30 seconds, A sends the short message to B.number
      Then within 120 seconds, B receives a short message from A.number as sms
    Then verify sms.text == "Hello, world"

The verify step ends with a failure, because there is a difference in the text sent and the text to be verified ("Hello, word" vs "Hello, world").

Test Case Example

Feature: SMS
  Scenario: SMS_originatedBasicSMS
    Given an Android phone as A
    And an Android phone as B
      And A composes a short message
      And A types "Hello, word"
      And within 30 seconds, A sends the short message to B.number
      Then within 120 seconds, B receives a short message from A.number as sms
    Then verify sms.text == "Hello, word"

The following report also points out where approximately the mistake is:

In this case, it is test instead of text.

Test Case Example

Feature: SMS
  Scenario: SMS_originatedBasicSMS
    Given an Android phone as A
      And an Android phone as B
    And A composes a short message
      And A types "Hello, world"
      And within 30 seconds, A sends the short message to B.local
    Then within 120 seconds, B receives a short message from A.number as sms
    Then verify sms.test == "Hello, world"

A few more examples of common spelling mistakes are:

Wrong	Right
"and an Android phone as A"	"And an Android phone as A"
"And within 30 seconds , A receives..."; "And within 30 seconds A receives..."	"And within 30 seconds, A receives..."
"Feature SMS"; "Feature. SMS"	"Feature: SMS"
"Given an android phone as A"	"Given an Android phone as A"

Solution: Missing characters

The following report shows that <callingParty> is missing from a Scenario Outline's Examples.

Test Case Example

Feature: Voice
  Scenario Outline: Voice_originatedBasicCall
    Given an Android phone as A
      And an Android phone as B
     When A dials the number B.number
      And within 5 seconds, B detects an incoming call from <callingParty>
      And after <ring> seconds, B answers the incoming call
      And within 5 seconds, A connects
      And after <dur> seconds, A ends the call and, within 10 seconds,
      he and B disconnect
   Examples:
    | dur | ring |
    | 10  |  3   |
    | 5   |  10  |

Whenever using test case variables (for example, <callingParty>), they must be defined in the Examples section of the Feature File.