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.
My son is learning to program. Last week he asked me to explain C# properties get and set and, as it turns out, it looks like many others are asking for the same. So, I’ve decided to spend the time on this post, explaining getters and setters in about as much detail as one can expect.
So here it goes…
Running Selenium in parallel from .NET seems to be a problem because, as of the time of this writing, I’ve yet to find a viable way of running selenium test on multiple browsers using Selenium Grid. This doesn’t mean that there aren’t a few articles out there that have some kind of solution. But they’ve never satisfied me as something that I could easily plug into my already created test.
While my preferred testing tools are NUnit and SpecFlow, the method I am about to propose should work with any existing test harness you might want to use. The only prerequisite is that you are using Page Models to wrap your access to any particular web page.
This article assumes that you already:
- know how to write Selenium tests
- know how to use Selenium Grid
- know how to use the Page Model pattern
- know how to use your chosen test harness.
OK. On to the main event. Continue reading “Running Selenium In Parallel With Any .NET Unit Testing Tool”
In the last post I mentioned there were a few topics we need to close up today. The two topics we’ve left undone are popping the attribute information off the stack when we hit a closing element and dealing with the paragraph gap that normally appears between paragraph elements.
While this isn’t specifically targeted at iTextSharp, which we’ve been covering in recent posts, this is really the closest book you are going to find on the subject.
The basics are the same. Keep in mind that the main difference is that setPropertyName and getPropertyName methods have been changed to .NET style properties (versus Java style) where it makes sense. Method names start with a capital letter in iTextSharp, and event wiring is a little funky (we’ll get to that later).