Open
Conversation
Looks like they changed this one, too. However, something else is going on that's stopping this change from being sufficient. The report says that the button is staying disabled and so we can't click on it.
Contributor
Author
|
Something I just noticed is that you say to use commands like "mvn verify", but those commands won't work for most people because most people don't have maven installed.
Two approaches come to mind:
|
Contributor
Author
|
Another thing you might consider is turning headless off for this first test. I'm not sure first-timers are better off flying blind. (Especially in the current situation where the first test instructions are broken). |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

While trying to follow the "Your First Web Test", I noticed that it wasn't working for me.
I looked into it and found that those selectors don't exist anymore; I've replaced them here with ones that do.
However, even with the good selectors, the submit button stays disabled.
I figure this could be a security measure from DDG—or maybe just a bug.
To get around this, you can just send enter, I suppose
$("#searchbox_input").sendKeys(Keys.ENTER);