If you're an absolute beginner with TDD, and you're looking to get a feel for how it all works. I'd recommend getting familiar with the Red, Green, Refactor cycle.
Red: Write a test that fails.
it('returns 3 when given 1 and 2',()=>{expect(calculator.sum(1,2)).toEqual(3)})
Green: Write the minimum amount of code to make that test pass.
classCalculator{sum (){return3}}
Refactor: Clean up the code you just wrote, if you need to.
then do it again...
Red:
it('returns 4 when given 2 and 2',()=>{expect(calculator.sum(2,2)).toEqual(4)})
Green:
classCalculator{sum (num1,num2){returnnum1+num2}}
Refactor: It's still pretty clean, so we won't.
Once you've got your head around that pattern. Have a look at something like this. Little, time-boxed, problems like these are great for building the habit of TDD.
An important thing to note here is that these examples are intentionally simple. Starting to write a .sum() method that just returns a fixed number doesn't make a whole lot of sense in the real world. But it helps to train your brain to start as simple as possible with your features and implementations. After a few runs through a few examples, you can just forget about starting that simple.
You can start working on these types of problems with just plain ol' JS and a test framework like Mocha or Jest.
If you're interested in a deep dive and you've got some spare cash, this is the book.
As a Senior Software Engineer, I specialize in software design, architecture, and documentation. I have a proven track record of working with popular technologies and I love the startup world
If you're an absolute beginner with TDD, and you're looking to get a feel for how it all works. I'd recommend getting familiar with the Red, Green, Refactor cycle.
Red: Write a test that fails.
Green: Write the minimum amount of code to make that test pass.
Refactor: Clean up the code you just wrote, if you need to.
then do it again...
Red:
Green:
Refactor: It's still pretty clean, so we won't.
Once you've got your head around that pattern. Have a look at something like this. Little, time-boxed, problems like these are great for building the habit of TDD.
An important thing to note here is that these examples are intentionally simple. Starting to write a .sum() method that just returns a fixed number doesn't make a whole lot of sense in the real world. But it helps to train your brain to start as simple as possible with your features and implementations. After a few runs through a few examples, you can just forget about starting that simple.
You can start working on these types of problems with just plain ol' JS and a test framework like Mocha or Jest.
If you're interested in a deep dive and you've got some spare cash, this is the book.
Thank you, the Red Green Refactor technique summarize it all... :)