1. WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here.here These slides contain a lot of animations. For optimal results, watch in slideshow mode.

2. How long will they take to catch all fish? a)Less than 1 hour b)Around 1 hour c)About 100 hours d)Forever fish {a|b|c|d} e.g. fish c fish {a|b|c|d} e.g. fish c 77577 [Extra] 100 fish If 100 people trying to catch 100 piranha fish in a lake. On average, one person can catch one fish within 1 hour

3. [Extra] 100 fish

4. System testing SUT

6. System testing SUT

7. System testing SUT

8. Do you want maximum publicity for your mistakes? [Extra] who wants maximum publicity

9. Do you want maximum publicity for your mistakes?

10. Never too early to test: An Introduction to Early Developer Testing CS2103/T, Lecture 4, Part 2, [Sep 6, 2013]

11. UI MSLogic Storage History UI MSLogic Storage History

12. UI MSLogic Storage History UI MSLogic Storage History

13. UI MSLogic Storage History SUT Unit testing

14. UI MSLogic Storage History SUT Unit testing

15. UI MSLogic Storage History SUT Stub Test Driver Unit testing

16. UI MSLogic Storage History SUT Stub Test Driver String getItem (int key){ if(key==1) return “Item for key 1”; if(key==2) return “Item for key 2”; … Unit testing

17. UI MSLogic Storage History SUT== MSLogic Stub Test Driver String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); … Unit testing

18. String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); … assertEquals(msLogic.getItem(1), “Item1”); …

21. UI MSLogic Storage History

22. UI MSLogic Storage History

23. UI MSLogic Storage History

24. UI MSLogic Storage History

25. UI MSLogic Storage History

26. SUT

27. Write a failing test Write code to pass test

28. CityConnect.java CityConnectTest.java

29. CityConnect.java CityConnectTest.java

30. CityConnect.java CityConnectTest.java Clementi --- Eunos Eunos --- Novena Clementi  true Novena  true Eunos  true Changi  false

31. CityConnect.java CityConnectTest.java

32. CityConnect.java CityConnectTest.java

33. CityConnect.java CityConnectTest.java

34. CityConnect.java CityConnectTest.java

35. CityConnect.java CityConnectTest.java

36. CityConnect.java CityConnectTest.java

37. CityConnect.java CityConnectTest.java

38. CityConnect.java CityConnectTest.java

39. CityConnect.java CityConnectTest.java

40. CityConnect.java CityConnectTest.java

41. CityConnect.java CityConnectTest.java

42. CityConnect.java CityConnectTest.java

43. CityConnect.java CityConnectTest.java

44. CityConnect.java CityConnectTest.java

45. CityConnect.java CityConnectTest.java

46. CityConnect.java CityConnectTest.java

47. CityConnect.java CityConnectTest.java

48. CityConnect.java CityConnectTest.java Note: more test cases required.

49. Write a failing test Write code to pass test

52. 60+ developers 75,000 Lines of Code

54. Automated tests

55. [extra] Mozilla patch policy 55

56. When the system test fails...

57. Must have automated developer tests!

58. Only system testing? NO It can save your career. Automated test driver frameworks Can do in TDD fashion Must do developer testing

59. Should do this too Everyone should do some Use these Do in CE2, Optional in project