Potential structure for the Workshop

[sohilpandya]

Hey @skibinska, Awesome work on the TDD Fizzbuzz challenge.

I am thinking that we can add to the three tests that you've done and follow it through to five:

QUnit.module( "FizzBuzz", function (assert) {
  QUnit.test( "when 1, returns 1", function (assert) {
    assert.equal( fizzbuzz(1), 1, "Test passed: returns 1" );
  });
  QUnit.test( "when 2, returns 2", function (assert) {
    assert.equal( fizzbuzz(2), 2, "Test passed: returns 2" );
  });
  QUnit.test( "when 3, returns Fizz", function (assert) {
    assert.equal( fizzbuzz(3), "Fizz", "Test passed: returns Fizz" );
  });
  QUnit.test( "when 4, returns Fizz", function (assert) {
    assert.equal( fizzbuzz(3), "Fizz", "Test passed: returns Fizz" );
  });
  QUnit.test( "when 5, returns Buzz", function (assert) {
    assert.equal( fizzbuzz(3), "Buzz", "Test passed: returns Buzz" );
  });
});

Make them just pass by if/else statements. then the code will be repetitive due to the if/else, so refactor it so that it returns Buzz for a 5 else returns Fizz. This will make it pass for any other number all the way to 10. (6..9 - will pass as well)

Then let them go off and solve the other part of it? (include FizzBuzz)

What are your thoughts, should we take them all the way to five tests or three tests should be ok?

[skibinska]

Five sounds good. :smile:

[skibinska]

We decided to show the students three example of code - the third one is a refactoring part, and then allow students to work in pairs.