Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for checking http codes #21

Closed
olimination opened this issue Jan 12, 2017 · 2 comments
Closed

Add support for checking http codes #21

olimination opened this issue Jan 12, 2017 · 2 comments
Milestone

Comments

@olimination
Copy link
Contributor

@olimination olimination commented Jan 12, 2017

Adding support for checking http codes.

This is useful if you want to check for example the existence of some resource.

This is also useful to test pure Web APIs with proper REST-oriented http codes.

There is for example a possibility to get it like this:

webRespone = webDriver.getClient.getCurrentWindow.getEnclosedPage.getWebResponse
webResponse.getStatusCode

Maybe this is a starting point.

@olimination olimination changed the title Add support for checking http codes or headers Add support for checking http codes Jan 12, 2017
@DaniRey DaniRey added this to the 3.0.0 milestone Sep 28, 2018
DaniRey added a commit that referenced this issue Sep 29, 2018
 - WebClientExposingDriver now provides access to response code and response headers
 - ResponseAccessors provides convenience methods to access this information
@DaniRey
Copy link
Collaborator

@DaniRey DaniRey commented Sep 29, 2018

Implementation is finished. Documentation has to be enhanced. This has to be done in the feature branch for 3.0.0 (otherwise our website documents 3.0.0 before it is released)

@DaniRey
Copy link
Collaborator

@DaniRey DaniRey commented May 31, 2019

Documentation is tracked with #79

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants