testing slideshare api

1. Grails Unit Testing By:- Uday & Imran

3. Understanding Unit Testing

4. Goals of Unit Testing

5. Spock Unit Testing

6. Writing Unit test cases

7. Demo

8. Exercise

12. Testing is destructive.The primary goal is to break the software

13. Very often the same person does coding and testing

14. Need 'split personality': when you start testing, become paranoid and malicious. Surprisingly hard to do: people don't like finding out that they make mistakes.

15. We have more code base to handle

17. Good Testing has high probability of finding as-yet-undiscovered errors

20. Integration testing (white box)

21. Functional testing (black box)

22. Acceptance testing

24. A unit is the smallest testable part of an application.

25. Each test case is independent from the others: substitutes like method stubs, mock objects, can be used to assist testing a module in isolation.

26. A unit test provides a strict, written contract that the piece of code must satisfy.

27. It tests individual methods or blocks of code without considering for surrounding infrastructure.

28. It is integral part of the development, so developers write unit test cases.

30. The actual database or external file is never tested directly by TDD.

31. It is highly reliant on Refactoring and Programmer skills

32. Not every code is testable.

34. Unit testing allows the programmer to refactor code at a later date, and make sure the module still works correctly

35. Simplifies integration

36. Unit testing may reduce uncertainty in the units themselves and can be used in a bottom-up testing style approach.By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

37. Documentation

38. Unit testing provides a sort of living documentation of the system

39. Design

40. When software is developed using a test-driven approach, the unit test may take the place of formal design. Each unit test can be seen as a design element specifying classes, methods, and observable behaviour.

41. Quality Improves the quality, readability and testability of the code

43. Based on Groovy

44. What makes it stand out from the crowd is its beautiful and highly expressive specification language

45. Getting started Basic Terms used in Spock

47. @Shared res =newVeryExpensiveResource()

48. static final PI = 3.141592654

50. def cleanup() {} // run after every feature method

51. def setupSpec() {} // run before the first feature method

52. def cleanupSpec() {} // run after the last feature method

53. Feature methods def "pushing an element on the stack"() { // blocks go here }

57. Example when: stack.push(elem) then: !stack.empty stack.size() == 1 stack.peek() == elem

58. Example when: def x = Math.max(1, 2) then: x == 2 expect: Math.max(1, 2) == 2

60. where block always comes last in a method expect: Math.max(a, b) == c where: [a,b,c] << [[1,2,2],[3,7,7]]

61. Exception conditions when: emptyStack.pop() then: thrown(EmptyStackException) emptyStack.empty

62. def &quot;testing exception is not thrown&quot;() { when: //something that does'nt throw an exception then: notThrown(NullPointerException) }

63. More annotations @Timeout @Ignore @IgnoreRest @FailsWith

65. small focused tests

66. doesn't load supporting components

67. doesn't spin up the whole Grails environment

68. dynamic methods and properties are not available

69. found under test/unit

71. All controller unit test case file extend ControllerSpec

72. All taglib tests files extend TaglibSpec

73. All integration test files extend IntegrationSpec

74. All integration test files for gsp extend GroovyPagesSpec

75. Specification is the super class of all

78. Mock() (SPOCK SPECIAL)

79. mockConfig()

80. mockForConstraintsTests()

81. mockLogging()

83. Injected methods mockDomain() gives us

84. All of your dynamic finders (findBy* and findAllBy* )

85. get(), getAll(), exists(), count(), list(), create(), save(), validate(), delete(), discard(), addTo(), removeFrom()

86. Injected methods that aren’t included:

87. countBy(), createCriteria(), executeQuery(), executeUpdate(), find(), findAll(), findAllWhere(), findWhere(), ident(), listOrderBy(), merge(), withCriteria(), withTransaction()

90. Returns an object of the class

91. MyService myService = Mock()

92. myService.someMethod(argument1,argument) >> result

93. myService.someMethod(_) >> result

96. Person person = new Person()

97. person.name = name

98. person.bankAccount =config.bank.accountNumber

99. person.save()

100. }

104. def “test my method which uses logging”() {

105. mockLogging(EmployeeService, true)

106. //

107. }

111. mockResponse

112. mockSession

113. forwardArgs

114. redirectArgs

115. renderArgs

116. mockParams

118. Test Def “test my simple action ”() { Setup: mockDomain(BankFile, [new BankFile(id: 1)]) BankFileService serviceMock = Mock() serviceMock.commit(params) >> new BankFile(id: 1) } controller.bankFileService = serviceMock when: mockParams.id = 1 controller.commit() then: redirectArgs.action==”show” redirectArgs.id==1 }

123. http://www.grails.org/Unit+Testing

124. http://meetspock.appspot.com/?id=9001

125. http://code.google.com/p/spock/wiki/SpockBasics

126. http://code.google.com/p/spock/wiki/Interactions

127. http://www.grails.org/doc/1.1/guide/9.%20Testing.html

128. http://www.make-go-now.com/2009/04/17/ode-to-mockformarch-part-2-mockdomain/

129. http://www.make-go-now.com/2009/03/05/ode-to-mockformarch-part-1-testing-constraints/