Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COGood thinking, I added a ImplicitlyWait of up to 10 seconds. It did not solve my problem yet though. I found out that the complete colorbox div was not locatable by Selenium. At pageload this div is hidden offcourse, but the driver.findElement(By.cssSelector("p.add")).click(); call should 'unhide' the colorbox div. This make take a while, but the the way I understood it the ImplicitlyWait setting gives this element up to 10 seconds to appear in the DOM. Does anyone know what may cause the colorbox div (and it's sub-elements) not to be locatable by Selenium?
      singulars
    2. COIs it possible, that there are two divs with equal ids `profielpagina_add`? Also you can always check if your colorbox located correct with Firebug and selenium IDE. If it not, then the problem is that you use incorrect locator. Otherwise you can increase waiting time to e.g 20 seconds, or if it the only slow part of your tests use Explicit wait
      singulars
    3. COThanks for the reply! There is only one div with the id 'profielpagina_add'. The problem is that this div is within a div with id 'colorbox', and this whole 'colorbox' div is not found by Selenium when I test for its presence. I tried using an explicit wait of 20 seconds (or even 40 seconds) after clicking the link that opens the colorbox before testing for presence of a div with id 'colorbox', but this results in a timeout of the explicit wait. When I click the link that opens the colorbox outside Selenium, it opens almost instantly, so the time shouldn't be the cause. Any more ideas maybe?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload