Tag: software-development
-
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: 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…
-
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…
-
Simplify Your Tests and Save Time: A Guide to Test Data Builders
Test data builders provide a solution to the time-consuming and complex task of setting up test scenarios. By pre-populating domain objects with valid data, developers can easily modify and reuse data for their tests. This technique not only simplifies the test setup process but also significantly improves the readability and maintainability of the test code,…
-
How to make your test case easy to understand by using test naming conventions
Introduction A common problem developers have is how to write the test name. Most projects don’t follow a convention, making the test cases a real mess! Every developer chooses a different approach because there are no set rules. Having a standard test naming convention will help you end this problem! When you write meaningful tests,…