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 [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour

3. How long will they take to catch all fish? a)Less than 1 hour b)Around 1 hour c)About 100 hours d)Forever [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour

4. How long will they take to catch all fish? a)Less than 1 hour b)Around 1 hour c)About 100 hours d)Forever [Extra] 100 fish If 100 people trying to catch 100 piranha fish. On average, one person can catch one fish within 1 hour

5. System testing SUT

7. System testing SUT

8. System testing SUT

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

10. Do you want maximum publicity for your mistakes?

11. Never too early to test: An Introduction to Early Developer Testing

12. UI MSLogic Storage History UI MSLogic Storage History

13. UI MSLogic Storage History UI MSLogic Storage History

14. UI MSLogic Storage History SUT Unit testing

15. UI MSLogic Storage History SUT Unit testing

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

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

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

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

20. String item = msLogic.getItem(1); if(!item.equals(“Item1”) print(“Case 1 failed”); … assertEquals(msLogic.getItem(1), “Item1”); JUnit (Java) Visual Studio Native Tests (C++)

23. UI MSLogic Storage History

24. UI MSLogic Storage History

25. UI MSLogic Storage History

26. UI MSLogic Storage History

27. UI MSLogic Storage History

28. UI MSLogic Storage History

29. SUT

31. Write a failing test Write code to pass test

32. CityConnect.java CityConnectTest.java

33. CityConnect.java CityConnectTest.java Clementi, Eunos, 20 Eunos, Novena, 40 Clementi  true Novena  true Eunos  true Changi  false Write the java/c++/pseudo code for the above

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

49. CityConnect.java CityConnectTest.java

50. CityConnect.java CityConnectTest.java

51. CityConnect.java CityConnectTest.java Note: more test cases required. Refactor as necessary.

52. Write a failing test Write code to pass test

53. [extra] Mozilla patch policy 53

54. [Extra] who wants maximum publicity Do you want maximum publicity for your mistakes? When the system test fails...

55. Must have automated developer tests!

56. Only system testing? NO It can save your reputation. Use automated test driver frameworks Can do in TDD fashion Must do developer testing

57. Should do this too Everyone should do some Use these Try in CE2, Optional in project

58. Framework Platform Specify requirements… Textual descriptions Feature list User stories Use cases OO domain models Object diagrams State machine diagrams Activity diagrams UI prototypes Glossary Supplementary requirements … Combat complexity… Use abstraction, build models System Detailed design BAC D Possible Improvements: Apply OO principles Apply analysis patterns Categorize and prioritize requirements Possible Improvements: ↑Cohesion, ↓Coupling Apply design patterns (Abstraction Occurrence, Singleton, Command, Observer) Apply design principles (Open/close, Law of Demeter, Separation of concerns, …) Use polymorphism (inheritance, interfaces, dynamic binding) Good product design guidelines (e.g., usability, …) Possible Improvements: Refactor code Coding standards and good coding practices Protect code using assertions, exceptions, logging, and defensive coding. Build automation Possible Improvements: Automate testing Use Test-Driven Development Increase efficiency and effectiveness of testing (Equivalence partitioning, Boundary Value analysis) Increase test coverage (function/entry/exit/statement/branch/ condition/path coverage) isolate SUT using drivers, stubs and dependency injection Unit testing Integration testing System testing Acceptance testing Alpha/beta testing Developer testing Made up as you go → Exploratory testing Predetermined → Scripted testing Can be created in these ways: o Black-box, Glass-box, Grey-box = Validation & Verification Testing Other V&V techniques: formal verification static analyzers code reviews … Unified process Agile processes B API (Application Programming interface) Architecture styles such as n- tier, client-server, peer-to-peer, broker, pipes-and-filters, service-oriented, transaction- processing, and MVC Top-down design Bottom-up design Integration Can be late-one- time, or early- and-continuous Can be top- down, bottom- up, sandwich, big-bang y x z yx z operations Class diagrams Sequential Iterative Breadth- first Depth- first Work-breakdown structures Project plans Team structures C A B D BA D Sequence diagrams Architecture After modifications… Regression testing Includes buffers and milestones Chief-programmer Egoless Strict hierarchy XP (Complex) Problem domain Establish requirements… brainstorming Focus groups User surveys Product surveys Observations Interviews Prototyping More agile -> less upfront detailed design ANALYSIS DESIGNIMPLEMENTATIONQUALITY ASSURANCE PROJECT MANAGEMENT Library QA User Issue trackers Detailed design Test cases Scrum CMMI RCS We use OO to ‘align the view’. We use UML as the standard notation. Stakeholders Requirements Specification System Specification IDEs, Debugging