because running from the toolbar may run tests from other open projects or all tests from a test class.

no difference

sure, try this List options = sortList.getOptions(); for (WebElement option : options) { try { System.out.println(option.getText()); }   catch(StaleElementReferenceException e) { System.out.println("StaleElementReferenceException");   }//catch }//for

what is normal run?

show me the code, David.

The visible text is indeed dynamic since the count can change: Make (any)Abarth (715)AC (18)Aixam (1)Alfa Romeo (1,713)Alpine (1)Ariel (7) So selecting the option by visible text does not work. But the value attribute is constant so you can select an option by value: Select list = new Select(element); list.selectByValue("ALFA ROMEO");

Hi David, I am assuming that you refer to the New, Nearly New and Used checkboxes from the autotrader.co.uk home page. If you cannot check them with the click() method of the WebElement type, try using javascript as follows: private final String NEARLYNEW_JS = "document.getElementById('oneSearchAdNearlyNew').click();"; private final String NEW_JS = "document.getElementById('oneSearchAdBrandNew').click();"; JavascriptExecutor jsExecutor = (JavascriptExecutor)driver; jsExecutor.executeScript(NEARLYNEW_JS); jsExecutor.executeScript(NEW_JS);

before() and after() methods are meant for setting up and clearing the test environment. creating the home page object, opening the home page, closing the results page is interaction with the application.

Some of the methods can look better. Can you say what does it mean for a results page to be valid? assertTrue(resultsPage.isValidPage()); Does valid mean that it can be displayed? Or that it shows the proper info? Or that it has results? Or something else? For the isSortOrderDescending() method, assertTrue(resultsPage.isSortOrderDescending(false)); what is the purpose of the false parameter? It is not clear why false is there so maybe it should not be used.

The test would be better if assertEquals() is used instead of assertTrue. So instead of assertTrue(resultsPage.countContains(homepage.searchCount())); assertTrue(resultsPage.isRadiusSelected(radius)); assertTrue(resultsPage.isPostalCode(postalCode)); assertTrue(resultsPage.isMakeSelected(make)); assertTrue(resultsPage.isModelSelected(model)); it should use assertEquals(resultsPage.count(), homepage.count()); assertEquals(resultsPage.radius(), radius); assertEquals(resultsPage.postalCode(), postalCode); assertEquals(resultsPage.make(), make); assertEquals(resultsPage.model(), model);

from friday afternoon to monday morning

sure, why not? but only if it is 100% yours :)

Hi Oleg, You should refrain from chaining methods of different classes for the following reasons: https://www.selenium-training-vancouver.com/forum/questions-public/do-not-chain-methods-of-different-classes Alex

Oleg, are all these methods from the same class? resultsPage.filters().model().change(model);

this is what i see: public void change(final String model) { try { select(model); filterMenuNumberResults = getFilterCount(); driver.click(driver.selectedElement()); } catch (WebDriverException e) { checkForModal(); change(model); } } The method does too many things. The method tries selecting a model. (one thing) Then the method tries getting the count. (second thing) Finally, the method clicks the selected element. (third thing) If any of these fail, it checks for the modal. (fourth thing) Finally, it calls itself to change the model (fifth thing). Recursive methods add complexity. So your method does 5 different things. Some of them are about interacting with elements. One is about getting a count and saving it in a variable that is not local. A method should do 1 thing only. It should either do something or return something. As far as I see, your method does 4 things and returns a value. Can you try simplifying it?

one question for you. what is the purpose of the change() method? what does it do?

for any random popup that is displayed always in the same position, the process of handling it is as follows: 1. check if the popup is displayed; this can be done by verifying if the popup title or another significant element is displayed; the checking should be done in a method that returns true if the popup is displayed and false otherwise 2. if the popup is displayed, dismiss it; this can be done usually by clicking the close icon of the popup 3. if the popup is not displayed, keep going

Example for assertTrue String title = "Vancouver Public Library"; boolean isEmpty = title.isEmpty(); //if the title is empty, stop the execution if (isEmpty == true) { System.out.println("title is empty!"); System.exit(1); } This is equivalent with String title = "Vancouver Public Library"; boolean isEmpty = title.isEmpty(); //if the title is not empty, continue the execution assertTrue("title is empty!", isEmpty == false); Example for assertEquals int count = 200; //if count is not positive, stop the execution if (count <= 0) { System.out.println("count is not positive!"); System.exit(1); } This is equivalent with int count = 200; //if the count is positive, continue the execution assertTrue("count is not positive!", count > 0);

I dont think that it is worth the effort.

I think that it is better to stay with one language, since Java and C# are very similar. I suggest that you learn a language as much as possible before trying others. Java has the bigger share of the test automation market in Vancouver.