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

Should not get GET and POST event logs #91

Closed
sswaroopgupta opened this issue Jul 11, 2018 · 2 comments
Closed

Should not get GET and POST event logs #91

sswaroopgupta opened this issue Jul 11, 2018 · 2 comments
Assignees

Comments

@sswaroopgupta
Copy link
Contributor

Description

When gauge tests are run should not get the GET and POST event logs

Steps to reproduce

  1. gauge init python_selenium
  2. gauge run specs

The events are displayed

Information that will help us debug

Gauge version: 1.0.1.nightly-2018-07-09
Commit Hash: 72109fa

Plugins
-------
python (0.3.4.nightly-2018-07-10)
@sswaroopgupta
Copy link
Contributor Author

Currently the output looks like

POST http://127.0.0.1:51091/session {"capabilities": {"alwaysMatch": {"goog:chromeOptions": {"args": [], "extensions": []}, "browserName": "chrome", "platformName": "any"}, "firstMatch": [{}]}, "desiredCapabilities": {"goog:chromeOptions": {"args": [], "extensions": []}, "platform": "ANY", "browserName": "chrome", "version": ""}}
Finished Request
# Customer Log out

   |name  |email                 |password|
   |------|----------------------|--------|
   |John18|john18.doe@example.com|password|
  ## Customer must be able to log out	POST http://127.0.0.1:51091/session/a098c51cb15b3e1ba62ad939c3b6548d/url {"url": "http://localhost:8080/", "sessionId": "a098c51cb15b3e1ba62ad939c3b6548d"}
Finished Request
 ✔No previous logins
 ✔POST http://127.0.0.1:51091/session/a098c51cb15b3e1ba62ad939c3b6548d/element {"using": "link text", "sessionId": "a098c51cb15b3e1ba62ad939c3b6548d", "value": "Sign up"}
...

The expected behavior is that these request events should not be shown.

@BugDiver BugDiver self-assigned this Jul 17, 2018
@BugDiver
Copy link
Member

The fix should be available in nightly >= 17-07-2018

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

No branches or pull requests

2 participants