Using automated tests.

Figure 174. Response to coding errors Slide presentation
Response to coding errors

Figure 175. Unit test concept Slide presentation

Figure 176. alarmClock(...) with errors Slide presentation
public class AlarmClock {
  /** Given a day of the week encoded as 0=Sun, 1=Mon,...
   */
  static  public String alarmClock(int day, boolean vacation) {
    switch (day) {
      case 1:
         ...
    if (vacation) {
      return "off";
    } else {
      return "10:00"; ...

The static keyword is required here as being explained in the section called “Class members and methods”.


Figure 177. Testing alarmClock(...) Slide presentation
public class AlarmClockTest {
  @Test 
  public void test_1_false() {
         Assert.assertEquals( "7:00", AlarmClock.alarmClock(1, false));
  }                                                            
  ...                                                          
                          Expected result               Input parameter
  @Test                                                        
  public void test_0_false() {                                 
         Assert.assertEquals("10:00", AlarmClock.alarmClock(0, false));
  }  ...

Figure 178. Testing alarmClock(...) details Slide presentation
public class AlarmClockTest {                    Input parameter
  @Test                                                  
  public void test_1_false() {                           
         final String result = AlarmClock.alarmClock(1, false);
                        ┗━━━━━━━━━━━━━━━┓
                                        
         Assert.assertEquals( "7:00", result);
  }                             
  ...                           
                    Expected result