-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
21 additions
and
1 deletion.
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 |
---|---|---|
@@ -1 +1,21 @@ | ||
# apiChallenges.github.io | ||
# Playwright API Testing Hub | ||
**Features** | ||
- Centralized Header Management: The fixture feature allows for the definition of shared headers in a single location, which are then applied across all relevant API requests. This centralization not only simplifies the codebase but also ensures consistency in header management throughout the test suite. | ||
- Reduced Code Duplication: By moving header logic to a base file, we have significantly reduced code duplication. This streamlining results in cleaner, more maintainable code, and reduces the risk of errors associated with manually updating headers in multiple places. | ||
- Improved Maintainability: Any changes to header configurations can now be made in one place, facilitating easier updates and ensuring that all test cases reflect the latest header requirements without requiring individual modifications. | ||
- Enhanced Readability: With common functionality abstracted away into fixtures, the test scripts themselves are more focused on the specific test logic, enhancing overall readability and making it easier for developers to understand and extend the test cases. | ||
**Limitations** | ||
Credentials: The test scripts hardcode authentication credentials, posing a security risk and reducing flexibility. | ||
- URLs: Endpoints and URLs are hardcoded, making the framework less adaptable to changes in the API environment or testing different environments. | ||
- Repetitive Code: Repetitive code structures are present, leading to maintenance challenges and potential test inconsistencies. | ||
|
||
<table> | ||
<tr> | ||
<td>Main</td> | ||
<td><a href="https://github.com/Cerosh/apiChallenges.github.io/tree/level.1">Level 1</a></td> | ||
<td><a href="https://github.com/Cerosh/apiChallenges.github.io/tree/level.2">Level 2</a></td> | ||
</tr> | ||
</table> | ||
# | ||
All the exercises I have used are the challenges that Alan Richardson created. He owns the demo application used to test the API. I want to thank him from the bottom of my heart for his efforts in creating these challenges and hosting this site free of cost for all new learners. | ||
https://www.eviltester.com/page/tools/apichallenges/<br> |