default behavior for `Wait` produces awkward logging

Open
#54 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start by locating the implementation and logging path for Wait.for_(TARGET), then compare it with Wait.for_(TARGET).to_appear(). Update the default log output so it is as readable and consistent as the to_appear() form, and verify both calls produce the intended messages.

Written by the indexing model from the issue text.

Description

actor.will(Wait.for_(TARGET))

The above call to wait will produce the following log message

Marcel waits up to 5 seconds using visibility_of_element_located with [target]

When you call the action using to_appear() the logging looks nicer, even though these are effectively identical actions.

actor.will(Wait.for_(TARGET).to_appear())

Marcel waits up to 5 seconds for the target to appear...
Dominant language
Python
Stars
7
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ScreenPyHQ/screenpy_selenium

All issues in ScreenPyHQ/screenpy_selenium

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.