Skip to content

Commit

Permalink
Update API-Testing-Guidelines.md
Browse files Browse the repository at this point in the history
Fix feature filenames examples
  • Loading branch information
jlurien committed Jun 14, 2024
1 parent 80c8547 commit d979509
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions documentation/API-Testing-Guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,8 +112,8 @@ E.g.:
Filename:

- APIs with a single feature file will use the api-name as file name: E.g. `location-verification.feature`
- For APIs with several operations that split the test plan in one feature file per operation, recommendation is to use the `operationId` as file name: `createSession.feature`.
- APIs with several feature files, not split by operation, should use the api-name along some other description, e.g.: `qod-notifications.feature`
- For APIs with several operations that split the test plan in one feature file per operation, recommendation is to add the `operationId` to the api-name as file name: `quality-on-demand-createSession.feature`.
- APIs with several feature files, not split by operation, should use the api-name along some other description, e.g.: `quality-on-demand-notifications.feature`

### Feature structure <a name="feature-structure"></a>

Expand Down

0 comments on commit d979509

Please sign in to comment.