I'm writing a simple script and I want selenium to fail the script or at least log the errors that come in http response.
Stable Selenium versions (below 4) are not supporting such functionality.
It has no ability to read HTTP responses.
Tools like Rest Assured are used for such things.
You can use browsermob-proxy tool to achieve that. You only should understand that when you call a page is actually causes a lot of requests to (different) servers and each responds with its own code.
For example the code could look like:
#BeforeTest
public void setUp(){
/*
Create and start proxy instance here
Configure driver to use that created proxy here
*/
}
#Test
public void testHeaders(){
// Create a map that would be storing url-to-status association
// Use synchronized version of a hash map because
// proxy handles connections in parallel
Map<String, Integer> urlToStatuses = new ConcurrentHashMap<>();
// Configure handler that would be listening for responses
// and fill the map
browserMobProxy.addResponseFilter((response, contents, messageInfo) -> {
urlToStatuses.put(messageInfo.getOriginalUrl(), response.status().code());
});
// Call a page
driver.get("https://google.com");
// Test the code of required URL
Assert.assertEquals(urlToStatuses.get("https://google.com").intValue(), 200);
// Do no forget to clear the map before the next assertion
urlToStatuses.clear();
}
I get frequent errors regarding stale element reference when using Selenium with Java. The application I'm testing is using AngularJS 2.0. Sometimes explicit waits would solve the problem but most of the time it wouldn't. Can I ignore such errors in my tests? How I could implement this?
Avram,
As the application is using Angular JS, the application will load every time so that's the reason we will get stale element reference exception in some cases. Even I experienced the same issue while automating an application which is using Angular JS. Protractor tool is the best tool for this type of applications since Protractor has inbuilt waits so that we don't need to keep waits deliberately. The only way to overcome this issue is, place thread sleeps where you will find that exception every time. keep ignoring Stale element reference class in fluent wait code.
new FluentWait<WebDriver>(driver)
.withTimeout(Time, TimeUnit.SECONDS)
.pollingEvery(
Time,
TimeUnit.SECONDS)
.ignoring(NoSuchElementException.class)
.ignoring(StaleElementReferenceException.class)
.until(new ExpectedCondition<WebElement>() {
public WebElement apply(WebDriver driver) {
return driver.findElement(locator);
Angular porting with JAVA could be a closer fit for your case. Ignoring page state and AJAX ready events is not a stable solution. You can even implement Angular specific waits on your own, via JavascriptExecutor interfrace. It allows you to inject custom JS into your code, so manipulating the browser. Use it like this:
long start = System.currentTimeMillis();
((JavascriptExecutor) driver).executeScript(
"// your JS code here");
I've used those slides when I had to do it in Python, but the JS code remains the same. We are quite happy with the this solution.
Automating Single-page Applications (SPA) is a new challenge, one which will drive further improvements in Selenium WebDriver and associated frameworks.
In such scenarios, I borrow a method waitForAngularRequestsToFinish() from SerenityBDD:
public void waitForAngularRequestsToFinish() {
if ((boolean) getJavascriptExecutorFacade().executeScript("return (typeof angular !== 'undefined')? true : false;")) {
getJavascriptExecutorFacade().executeAsyncScript("var callback = arguments[arguments.length - 1];" + "angular.element(document.body).injector().get('$browser').notifyWhenNoOutstandingRequests(callback);");
}
}
What it basically does is using JavascriptExecutor execute an asynchronous script which notifies or returns only when there are no pending angular requests being processed.
I'm writing a program in Java to automate a web test of server management console URL's to find which ones present users with a box for login credentials.
I have begun looking into doing this with Selenium WebDriver to automate the actual test function of opening and closing windows, but what I can't figure out is how I should go about detecting whether or not the login box is presented to a user.
Is there a specific response code that the server presents when this happens? I know when a user is unauthenticated/forbidden there will be an HTTP response of 401 or 403, respectively, but I am not sure if this 401 unauthenticated response Code will happen regardless of whether or not a box for login credentials is presented to the user.
The goal is to find which URL's allowed a user the opportunity to type in credentials and then publish those to a .txt file for further evaluation. I already have the java I/O elements working properly to do this, so all I really need is to figure out what condition I'm looking for. Any help would be appreciated!
Given you have an instantiated WebDriver instance (driver)
and a collection of URLs (urls) you want to check,
and given your loginbox contains some element located by ID "username"
then one possible Selenium solution in Java could look like this:
for (String url : urls) {
driver.get(url);
//adjust to your needs: long timeOutInSeconds, long sleepInMillis
WebDriverWait wait = new WebDriverWait(driver, 120L, 1000L);
try {
wait.until(ExpectedConditions.presenceOfElementLocated(By.id("username")));
//TODO: Element found within timeOutInSeconds
} catch (WebDriverException e) {
//TODO: Element not present after timeOutInSeconds, write url to txt file
}
}
If you cannot locate the element by id, use other locating mechanisms as described here.
I am trying to develop a Suite of classes for testing my websites functionality every night and I do this in Chrome, Firefox, Edge and IE. Because sometimes Selenium doesn't find an element I need something that e.g. takes a screenshot of the browser before giving out an error. I don't need a function for taking a screenshot I need something that triggers when Selenium can't continue.
Best regards,
MK
If I understand correct, you need to set up the trigger for your another system, which can react on Selenium test error.
In your test code you can use :
try {
// find element and test code
} catch (NoSuchElementException e) {
// set up the trigger code
}
To notify another system you can choose any system, which can provide notification mechanism.
In your case, you could use for example Redis with pub/sub.
So your reaction system will be a subscriber and test - provider of the event.
What is the difference between get() and navigate() methods?
Does any of this or maybe another method waits for page content to load?
What do I really need is something like Selenium 1.0's WaitForPageToLoad but for using via webdriver.
Any suggestions?
Navigating
The first thing you’ll want to do with WebDriver is navigate to a page. The normal way to do this is by calling get:
driver.get("http://www.google.com");
WebDriver will wait until the page has fully loaded (that is, the onload event has fired) before returning control to your test or script. It’s worth noting that if your page uses a lot of AJAX on load then WebDriver may not know when it has completely loaded. If you need to ensure such pages are fully loaded then you can use waits.
Navigation: History and Location
Earlier, we covered navigating to a page using the get command (driver.get("http://www.example.com")) As you’ve seen, WebDriver has a number of smaller, task-focused interfaces, and navigation is a useful task. Because loading a page is such a fundamental requirement, the method to do this lives on the main WebDriver interface, but it’s simply a synonym to:
driver.navigate().to("http://www.example.com");
To reiterate: navigate().to() and get() do exactly the same thing. One's just a lot easier to type than the other!
The navigate interface also exposes the ability to move backwards and forwards in your browser’s history:
driver.navigate().forward();
driver.navigate().back();
(Emphasis added)
They both seems to navigate to the given webpage and quoting #matt answer:
navigate().to() and get() do exactly the same thing.
Single-Page Applications are an exception to this.
The difference between these two methods comes not from their behavior, but from the behavior in the way the application works and how browser deal with it.
navigate().to() navigates to the page by changing the URL like doing forward/backward navigation.
Whereas, get() refreshes the page to changing the URL.
So, in cases where application domain changes, both the method behaves similarly. That is, page is refreshed in both the cases. But, in single-page applications, while navigate().to() do not refreshes the page, get() do.
Moreover, this is the reason browser history is getting lost when get() is used due to application being refreshed.
Originally answered: https://stackoverflow.com/a/33868976/3619412
driver.get() : It's used to go to the particular website , But it doesn't maintain the browser History and cookies so , we can't use forward and backward button , if we click on that , page will not get schedule
driver.navigate() : it's used to go to the particular website , but it maintains the browser history and cookies, so we can use forward and backward button to navigate between the pages during the coding of Testcase
Not sure it applies here also but in the case of protractor when using navigate().to(...) the history is being kept but when using get() it is lost.
One of my test was failing because I was using get() 2 times in a row and then doing a navigate().back(). Because the history was lost, when going back it went to the about page and an error was thrown:
Error: Error while waiting for Protractor to sync with the page: {}
driver.get() is used to navigate particular URL(website) and wait till page load.
driver.navigate() is used to navigate to particular URL and does not wait to page load. It maintains browser history or cookies to navigate back or forward.
As per the javadoc for get(), it is the synonym for Navigate.to()
View javadoc screenshot below:
Javadoc for get() says it all -
Load a new web page in the current browser window. This is done using
an HTTP GET operation, and the method will block until the load is
complete. This will follow redirects issued either by the server or as
a meta-redirect from within the returned HTML. Should a meta-redirect
"rest" for any duration of time, it is best to wait until this timeout
is over, since should the underlying page change whilst your test is
executing the results of future calls against this interface will be
against the freshly loaded page. Synonym for
org.openqa.selenium.WebDriver.Navigation.to(String).
navigate().to() and get() will work same when you use for the first time. When you use it more than once then using navigate().to() you can come to the previous page at any time whereas you can do the same using get().
Conclusion: navigate().to() holds the entire history of the current window and get() just reload the page and hold any history.
For what it's worth, from my IE9 testing, it looks like there's a difference for URLs that contain a hashbang (a single page app, in my case):
http://www.example.com#page
The driver.get("http://www.example.com#anotherpage") method is handled by the browser as a fragment identifier and JavaScript variables are retained from the previous URL.
While, the navigate().to("http://www.example.com#anotherpage") method is handled by the browser as a address/location/URL bar input and JavaScript variables are not retained from the previous URL.
There are some differences between webdriver.get() and webdriver.navigate() method.
get()
As per the API Docs get() method in the WebDriver interface extends the SearchContext and is defined as:
/**
* Load a new web page in the current browser window. This is done using an HTTP POST operation,
* and the method will block until the load is complete.
* This will follow redirects issued either by the server or as a meta-redirect from within the
* returned HTML.
* Synonym for {#link org.openqa.selenium.WebDriver.Navigation#to(String)}.
*/
void get(String url);
Usage:
driver.get("https://www.google.com/");
navigate()
On the other hand, navigate() is the abstraction which allows the WebDriver instance i.e. the driver to access the browser's history as well as to navigate to a given URL. The methods along with the usage are as follows:
to(java.lang.String url): Load a new web page in the current browser window.
driver.navigate().to("https://www.google.com/");
to(java.net.URL url): Overloaded version of to(String) that makes it easy to pass in a URL.
refresh(): Refresh the current page.
driver.navigate().refresh();
back(): Move back a single "item" in the browser's history.
driver.navigate().back();
forward(): Move a single "item" forward in the browser's history.
driver.navigate().forward();
driver.get("url") and driver.navigate( ).to("url") both are same/synonymous.
to("url") internally calling get("url") method. Please find the below image for reference.
Either of them does not store history - this is the wrong information that is available on most of the blogs/websites.
Below, statements 1, 2, and 3, 4 will do the same things i.e land in the given URL.
statemnt 1: driver.get("http://www.google.com");
statemnt 2: driver.navigate( ).to("http://www.amazon.in");
statemnt 3: driver.get("http://www.google.com");
statemnt 4: driver.get("http://www.amazon.in");
Only navigate() can do different things i.e. moving back, forward, etc. But not the to("url") method.
Otherwise you prob want the get method:
Load a new web page in the current browser window. This is done using an
HTTP GET operation, and the method will block until the load is complete.
Navigate allows you to work with browser history as far as i understand it.
Both perform the same function but driver.get(); seems more popular.
driver.navigate().to(); is best used when you are already in the middle of a script and you want to redirect from current URL to a new one. For the sake of differentiating your codes, you can use driver.get();to launch the first URL after opening a browser instance, albeit both will work either way.
CASE-1
In the below code I navigated to 3 different URLs and when the execution comes to navigate command, it navigated back to facebook home page.
public class FirefoxInvoke {
#Test
public static void browserInvoke()
{
System.setProperty("webdriver.gecko.driver", "gecko-driver-path");
WebDriver driver=new FirefoxDriver();
System.out.println("Before"+driver.getTitle());
driver.get("http://www.google.com");
driver.get("http://www.facebook.com");
driver.get("http://www.india.com");
driver.navigate().back();
driver.quit();
}
public static void main(String[] args) {
// TODO Auto-generated method stub
browserInvoke();
}
}
CASE-2:
In below code, I have used navigate() instead of get(), but both the snippets(Case-1 and Case-2) are working exactly the same, just the case-2 execution time is less than of case-1
public class FirefoxInvoke {
#Test
public static void browserInvoke()
{
System.setProperty("webdriver.gecko.driver", "gecko-driver-path");
WebDriver driver=new FirefoxDriver();
System.out.println("Before"+driver.getTitle());
driver.navigate().to("http://www.google.com");
driver.navigate().to("http://www.facebook.com");
driver.navigate().to("http://www.india.com");
driver.navigate().back();
driver.quit();
}
public static void main(String[] args) {
// TODO Auto-generated method stub
browserInvoke();
}
}
So the main difference between get() and navigate() is, both are
performing the same task but with the use of navigate() you can move
back() or forward() in your session's history.
navigate() is faster than get() because navigate() does not wait for
the page to load fully or completely.
driver.get(url) and navigate.to(url) both are used to go to particular web page. The key difference is that
driver.get(url): It does not maintain the browser history and cookies and wait till page fully loaded.
driver.navigate.to(url):It is also used to go to particular web page.it maintain browser history and cookies and does not wait till page fully loaded and have navigation between the pages back, forward and refresh.
To get a better understanding on it, one must see the architecture of Selenium WebDriver.
Just visit https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol
and search for "Navigate to a new URL." text. You will see both methods GET and POST.
Hence the conclusion given below:
driver.get() method internally sends Get request to Selenium Server Standalone. Whereas driver.navigate() method sends Post request to Selenium Server Standalone.