-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Loading status checks…
feat: add basic gherkin test suite for tracking
Signed-off-by: Bernd Warmuth <[email protected]>
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
Feature: Tracking | ||
|
||
# This test suite contains scenarios to test the tracking API. | ||
|
||
Background: | ||
Given a provider is registered | ||
|
||
Scenario Outline: Invalid event names | ||
When an event was tracked with tracking event name <event_name> | ||
Then nothing should have been tracked | ||
And the tracking operation shall error | ||
Examples: Basic | ||
| event_name | | ||
| "" | | ||
| "NULL" | | ||
|
||
Scenario Outline: Provider's track functionality is called | ||
When an event was tracked with tracking event name <event_name> | ||
Then the tracking provider should have been called with event name <event_name> | ||
Examples: Basic | ||
| event_name | | ||
| "the-event" | |