How much understanding do you have in economics? Because, most of our work, in software, is really based on economics decisions. When we’re coding, we’re working to deliver some economic value to the organization. Coding is only half the fun, though. In fact, it’s really a lot less then half. Read more…
Throughout history, since the cavemen of old, we were looking for signs of quality. There was one way to do that: Look at the final product and decide. But that takes time. Plus if your work is being assessed only after you won, and the mammoth lost, that’s a bit Read more…
Code reviews are very important. They are the last line of defense. Code review is the last chance we have to stop a problem from going out into the wild. Whatever that problem is, whether it’s a bug hiding in the bushes, or in plain sight. Or a problem that Read more…
I really like this topic. Test design is something we many times skip, or just gloss over. For example, I have a test for some API, and I need to write the next one. Chances are I’m going to reuse what I can from the setup, modify only what needs Read more…
Whether you’re a tester, or a developer, or a manager, you’ve probably wondered at some point in your life – what makes apps so complex? Where does all the complexity come from? It’s complex to build, to test, to deploy, to ship a quick bug fix. All of the above. Read more…
If you take a look at automated web testsת you’ll be overwhelmed by locators (or selectors, or elements, or whatever framework you’re using). They are everywhere, and the tests find them and make use of them. As they should. It’s not surprising, because most of web automation is locating objects Read more…
What test types do we have? Unit tests. API tests. Component tests. E2E tests. We have all kinds. The names can be a bit confusing, though.Like, what is really a unit? Is it a method, or a class? Maybe more than two classes? When are we crossing into component tests Read more…
How do we approach API test planning? We usually look at the API and what it does, and check it’s functionality, along with a few more APIs. And we consider the API testing done. But we miss out on what we can really test. Our goal is to report on Read more…
Design patterns are very useful. They help us create readable and maintainable code. But there’s only one pattern that has gone on to garner infamy. Some people might call using it a moral failure: The evil Singleton. So how much damage must one pattern do to win that title? Since Read more…
Every unit testing example starts with a calculator, so let’s do that today. Have a look at this code. Suspicious eh? Okay, so how many tests do you think we need to cover this code? “Cover” is pretty vague. How many as in “enough tests that you feel comfortable leaving Read more…