There are two twin evils that I see in the programming community. The first is the programmer who knows what he knows and has no desire to learn more. I call these, “coasters”. And then there are the programmers who are so curious that they try to learn every new thing that comes along, with no focus. The interesting thing is, both of these types of people end up at the same place. Out of work. The cure for both is the same. Being Awesome.
I’ve been using the CefSharp.Offscreen library to drive the Chromium browser for a couple of months now. While the code I’ve been working on has been working correctly, I could never figure out why so many instances of Chromium are left dangling in my task manager. Oh, they’d all go away once I exited the application, but then it would take a very long time for my application to completely close because there were so many instances of Chromium hanging around.
This past week, I finally figured out how to keep the number of Chromium instances in line with the number of off-screen browser windows I was actually creating.
So, once again, the place I am currently working has been interviewing for some more programmers and we’ve had to laugh at some of the answers we’ve received on some pretty simple question.
And that naturally got us all talking about good interview questions. How can we tell that the applicant is even worth interviewing?
The following questions are not meant to be THE interview. The questions are meant to shorten the interview process by ensuring the applicant has a basic understanding of the language they will be expected to work with.
Today, what I want to offer is how I overcame various hurdles related to testing EXTjs with Selenium.
This probably doesn’t happen all that often, but this last week I came across the need to know which browser I was running my selenium test against. I figured that buried deep in the object structure of Selenium, there MUST be a way of finding out what browser I was currently running. As it turns out, I was right.