Manual testing versus automated testing # Should you test manually or let a computer take over? It's important, however, not to fall into binary thinking here. When answering the question of how to test, the first point to clarify is very abstract. Let's go! 🙌 Start with the basics: General testing modes # In later articles, we will answer the second question, combine the answers, and find the testing strategy that works best for your project.
To start from a common ground, let's first learn what testing modes exist and then focus on the common types of testing. This article focuses on the general things you need to know to answer the first question. To approach the topic of how to test practically, let's start with a clean slate and answer two basic questions: Simply put, you need a plan before you start writing the actual test code. As a very first step, you need to determine what parts of the application quality you need to ensure and how you can achieve that. Writing some tests is crucial but it's only one part of the ideal test setup for your project.
The units may work well on their own but not in relation to each other. You want both drawers to work well with each other and be operable at the same time.Īpply this to web development: you wrote some tests, maybe even achieved 100% test coverage, but your application still needs to work once other parts fall into place. This meme sums it up quite nicely: each drawer works perfectly well individually, but in combination with the other drawer, they block each other and fail to function. We've all been there: what is a recurring coding meme that happens all too often in real life? Testing in all shapes: How does this all work together?.Test automation types: How do you want to test?.Manual testing versus automated testing.Start with the basics: General testing modes.
0 kommentar(er)
