trial and errors are key to building anything new and innovative.
1. Test-Driven Development is Fundamentally Wrong
It sounds backwards because it really is
2. PHP Test Driven Development Part 1: Introduction
Test Driven Development is a coding practice where you write a test first then write the code to pass that test, usually in short iterative cycle.
3. How I learned to stop worrying and love TDD
It’s almost unanimous in the articles and studies on the internet these days: Test-driven development (henceforth, TDD) is the way developers should be creating everything. But if you’re like me, getting started is a lot harder than it sounds.
4. Implementing basic Component tests using Jest and Enzyme
This is the first of maybe a couple of posts that I am going to be doing on testing React components and TDD in general. This one deals with setting up the Jest and Enzyme libraries and then writing a couple basic tests for a Login component. In my next posts hopefully I’ll go into a little more detail about these libraries and about how we can test more complex components that involve Redux. So with that let’s get started!
5. Software Development is Not About Unit Tests
Photo by ShareGrid on Unsplash
6. Why Software Testing is So Important
It isn't about being diligent. It's because we've forgotten what we knew.
7. The Untold Truth of Test Driven Development
Your Practical Introduction to Test Driven Development
8. How to Use RSpec From Basics to Testing User Input
On my journey on Microverse, one of the things that troubled me the most to understand was RSpec, a Ruby gem for Test-Driven Development. The concept is quite simple. You create tests as you code along, so in the future, if an update breaks something, it will be easy to notice because one or more tests will fail.
9. Test-Driven Development with RSpec in Rails
When we start developing an app we usually do it the old fashion way: we get an idea, we elaborate on it, we make a plan to develop an app then we start coding and in the end, we test if our app is working properly.
test-driven-development
Photo credit, HackerNoon AI
Top comments (0)