Category: best pratices
-
Structural-Based Testing: Filling the Gaps in Your Test Suite
When writing tests for your code, it’s easy to miss some parts, which can lead to bugs. How can you ensure you’ve tested everything properly? Use structural-based testing! What is Structural-based testing? This technique is about considering your code when writing your tests. It’s a complementary technique and should be used as a support of…
-
Specification-Based Testing: Devise test cases
This is the last part of the specification-based testing series. Now we are going to put all of the knowledge that we gained from the other steps and start creating our tests efficiently. If you followed every step, you already have questioned and prepared the scenarios that will help catch as many faults in your…
-
Specification-Based Testing: Analyze boundaries
When conducting specification-based tests, analyzing boundaries is crucial. Boundaries, such as inclusive and exclusive intervals, often harbor bugs. For instance, in the CHIP-8 emulator code, the boundary condition for the carry flag at exactly 255 requires thorough testing. Testing exact, minus one, and plus one boundary values is essential to identify potential bugs and clarify…
-
Specification-Based Testing: Exploring partitions
When we are testing our code, we can’t only test things that will give us a successful return. Tests should be a way to help you find bugs, so in this step of the specification-based testing, we are going to understand the partitions of our code. And explore scenarios that could break our code or…
-
Specification-based Testing: Explore the program
The third step of the specification-based test is to explore the program behavior. You can skip this step if you wrote the code that you are testing. This step is a good way to understand code that you need to test but was not implemented by you. In this scenario, you don’t have the complete…
-
Specification-based Testing: Understand the requirements
Understanding the requirements is an important part of testing your code. If you already know the business rules you can create tests to validate it. Also, you can create some that will prevent unwanted behavior too. When writing tests, consider the inputs, how they affect the code, and if the results meet your business rules. Do you have some doubts about it? What should be the result in some…
-
Specification-Based Testing: A Developer’s Secret Weapont
One quick story: I was adding a new feature that needed an API client created by another developer. The API required three inputs: ID, country code, and phone number. I followed this specification, made a test, and all seemed good. But when I updated my code later before deploying. I found out the other developer…
-
Friction: How Human Behavior Influences Code Development
Introduction Have you ever tried to start a gym routine, learn a new skill, or start a new side project, and found yourself failing? The reasons for failure can sound familiar: This problem, where obstacles prevent us from starting something new, is known as friction. Friction in Software Development What does friction have to do with…
-
Less Code, More Tests: Exploring Parameterized Tests in JUnit
Introduction Regarding writing tests, some developers are lazy writing fewer test scenarios as possible. And sometimes they can write no scenarios at all. Imagine being able to test many scenarios without writing much code. Isn’t that great? A parameterized test lets you test many scenarios. You just send a list of parameters. This way, you…
-
How to test complex conditions with the MC/DC criteria
Introduction Have you needed help defining what to test when you encounter a complex condition in your code? Do you feel lazy when looking at a condition that has too many logical statements? It’s easy to look at that big if statement that you find in legacy code and think: “Man, what should I test…