Tagged: testing

I had an interesting discussion today that I think is worth writing about. I mentioned having a problem with having a very fat component in a system since integration tests usually become a nightmare. The idea was raised that architecture should not be driven by integration tests, but rather by customer requirements and value. While at face value, this seems intuitively correct, is that so?

After a lot of work, the Germanium Selector Builder Chrome Plugin is finally completed. It's now available on the Chrome Store as both a Free and a Pro Version.

After the article from yesterday where we got to see some code where code duplication actually improved the tests, we'll look at something similar today, but this time in unit tests, and why I'm not a big fan generally speaking of test parametrization.

Sometimes there's no end in sight. You have the map to navigate around the code, but the sheer complexity of the thing makes finding that one bug evasive. It's time for Scientific Testing.

After we can build our code, it's time to start addressing making changes. Now, not all code is created equal, and there are better ways to move around than simply opening every single file. Let's see how.

In the next miniseries of articles we're going to deal maintaining Legacy Code. We'll go with how to absorb faster bigger portions of code, how to reason larger codebases, and general day to day life. Since there's no one size that fits all, your mileage will vary.

Python has bundled into it a rather decent testing framework, that resembles a lot JUnit, named unittest. This is packaged in the core python, and it's simple to use. While I'm a big fan of Behave, sometimes, especially if testing low-level APIs, it's less verbose to just write a core python unit test. In this article we explore how to create our first test.

Testing a website for accessibility might prove challenging. Fortunately with the advent of some opensource tools, it's easier to test for problems, but automating this is a challenge. In this article we'll explore how to setup a Jenkins pipeline that runs pa11y - a popular opensource accessibility checker - inside a docker container.

As we enter 2019, I am using clouds a lot - the Germanium infrastructure is on Kubernetes, my last project was on AWS, I stopped using Java in my personal projects, and started learning Cobol for work. Here's why.

One of the most time consuming things for this website, was cleaning up the tags. They used to be an unorganized mess, and I was adding new ones as I was writing new articles. A lot of the tags had a single article. Some were misspells of an existing tag. A strangely disconnected cloud of tags existed, and wasn’t exactly clear what connected where. At some point I just realized this has got to stop.