Skip to content

Commit

Permalink
api test failure (#81)
Browse files Browse the repository at this point in the history
### To be filled by the PR creator:

* A brief description of the changes made - 

* Do we have clean latest run report (Docker or Browserstack) attached
with this PR?
  * [ ] Yes
  * [ ] No (Please explain why)

* Does the PR contain changes to any core file?
  * [ ] Yes (Needs approval from at least 1 people)
  * [ ] No

* Is it
  * [ ] New Testcase
  * [ ] Fix


### To be filled by the PR reviewer:

* [ ] Verify the attached run report passed in GitHub Actions (Docker or
Browserstack run)

* General
    * [ ] Use the best strategy to locate the elements
    * [ ] Comments wherever the code is not readable by itself
    * [ ] Use of the right data structure for the use case
    * [ ] Reuse logic/functionality as much as possible
    * [ ] Cleanup of any test data that is generated by the tests
    * [ ] No static waits
  • Loading branch information
Tauqir Sarwar authored Apr 3, 2024
2 parents 6b0874b + 2c3cd10 commit 8446773
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion frontend/test_project/features/api/api_tests.feature
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Feature: Test HTTP methods for a REST API
Given I set the GET endpoint to '/posts' for fetching posts
When I send a GET HTTP request
# Failing the test on purpose to see the failure in the report
Then I expect the HTTP response code of 'GET' to be '200'
Then I expect the HTTP response code of 'GET' to be '2000'
And I expect the response body of 'GET' to be non-empty

@api_smoke
Expand Down

0 comments on commit 8446773

Please sign in to comment.