I’ve had two incidents recently that have shown me how TDD impacts Software Architecture. Both of these are with code I’m working on.
What Software Architecture Might Do
Software architecture might specify how is put together at a very high level. For example, software architecture might specify that we use a three tiered approach or an n-tiered approach. This approach places our view code is at one level, our business rules are at another level, and our data access at yet a third level.
Continue reading “Software Architecture without Test Driven Development is DANGEROUS!”
I’ve been frustrated lately by the flippant use of the words “Scrum” and “Agile” in our industry. They’ve officially made it to the point of “buzzwords that mean nothing” that get slapped onto job requirements like the typical requirements we’ve all seen.
Continue reading “You Aren’t Doing Scrum If…”
Here is a rebuttal.
My experience with setting up Selenium Grid was frustrated by the lack of information available about exactly what I needed to do to get this working.
I’ve actually had this working for a while now and I’ve set it up, or helped others set it up now, several times. So, I guess it is time to write a post about it so I can just send people here when I need to explain the setup.
Note, the following discussion already assumes you know something about how to use Selenium without the Grid so there won’t be a lot of code here other than what is need to get the Grid up and running so you can run your test on it.
Continue reading “Selenium Grid Setup”
A while ago I wrote an article explaining what SpecFlow is, and why you might want to use it. I’ve been using it for several months now and I’ve recognized several patterns that have emerged in my usage that I wish I had known when I started, so I thought I’d share them with you today.
Continue reading “SpecFlow Strategy”