This webinar has started out with a common topic I discuss in my workshops: Test types. People always want to know about what is a unit test vs. component test. But it goes deeper than that. Everybody knows what an API test is, but when you’re testing a whole service, Read more…
Some call them flaky tests. Some call them fragile tests. Or unstable. I say it’s neither, it’s the code. Nobody likes them, regardless. But here’s something interesting I heard in a conversation with one of my clients. He said: “I like calling them flaky tests, not fragile”. Why? I asked. Read more…
I don’t get tired of hearing that question, because if I did, I’d need to sleep for a couple of years. It usually comes up with unit tests, as developers prepare to test their day-old or year-old code. That question has a couple of hidden assumptions that are easily crushed, Read more…
Abstraction is one of the founding principles of software. In this post I describe UI component testing breaks through abstraction and causes fragile tests.
Abstraction is one of the founding principles of software. In this post I describe how interfaces are just one side of the problem in testing.
Abstraction is one of the founding principles of software. In this post I describe how mocks break abstraction and its effect on testing.
Abstraction is one of the founding principles of software. It allows us to simplify ideas, code and usage. It also impacts testing directly.
I was glad to go on the TestIL podcast a few weeks ago. We talked about testing in general, and API testing in more details.
The “API Exploratory Testing” recording from TestCon 2023. In this I talk about exploration, charters, session based testing, and demo a n exploratory session.
Clean tests are readable, maintainable, and helpful in case of failure- themselves, or their brothers. This webinar describes clean code and tests.