Spock
•
0 j'aime•286 vues
This presentation provides spock basics. It describes building blocks of spock feature methods. Also it provides code walkthrough.
Contenu connexe
En vedette
Similaire à Spock
Similaire à Spock (20)
Dernier
Dernier (20)
Spock
- 2. Agenda ● Benefits of unit testing ● Other testing framework ● Spock Basics ● Walkthrough
- 3. Benefits of unit testing ● Reduces bugs in production,reduces cost ● Reduces development time ● Increase confidence ● can executes test cases frequently ● Measures completion ● Provides documentations ● Improves design
- 4. Other testing frameworks ● JUnit ● TestNG
- 5. Spock Basics ● Specification ● Building blocks o Fields o Fixture methods o Feature methods o Helper methods
- 6. Spock:Fields ● Instance Fields def pageNo=0 def request = new GroupRequestDto() ● Shared Fields @Shared @AutoCleanup RESTClient restClient ● Static Fields static final SUCCESS=200;
- 7. Spock:Fixture methods ● def setup() {} ● def cleanup() {} ● def setupSpec() {} ● def cleanupSpec() {}
- 8. Spock:Feature methods ● setup ● when ● then ● expect ● cleanup ● where
- 9. Vs Junit Spock Junit Specification Test class setup() @Before cleanup() @After setupSpec() @BeforeClass cleanupSpec() @AfterClass Feature Test Parameterized feature Theory Condition Assertion Exception condition @Test(expected=...) @FailsWith @Test(expected=...) Interaction Mock expectation (EasyMock, JMock, ...)
- 10. Walkthrough
- 11. References ● Spock Basics https://code.google.com/p/spock/wiki/SpockBasics ● Benefits of Unit Testing http://sd.jtimothyking.com/2006/07/11/twelve-benefits-of-writing-unit- tests-first/
Notes de l'éditeur
- Specification: It describes expected feature/properties/functionality of the system under test. System can be a simple class or a complex application. Specification is groovy class and extends spock.lang.Specification. Name of the class mostly echoed the name of the system under test. Like GroupControllerSpec etc
- Instance Fields: It is used to shared object between fixture methods. Objects are not shared among feature methods. Each feature method gets its own copy of the instance fields. Thus features methods become isolated from each others. Shared Fields: Expensive objects are created once and shared across feature methods. Static Fields: Used only for constant.
- Fixture Methods: Responsible for setting up and cleaning up environments in which feature methods runs. All fixture methods are optional The setupSpec() and cleanupSpec() methods may not reference instance fields.
- Feature methods: Building block of specification. It describes the feature expected to be present in the system under specification. Blocks setup:The setup block is where you do any setup work for the feature that you are describing. when: then: The when and then blocks always occur together. They describe a stimulus and the expected response. expect: Conditions describe an expected state, much like JUnit's assertions. However, conditions are written as plain boolean expressions, eliminating the need for an assertion API. (More precisely, a condition may also produce a non-boolean value, which will then be evaluated according to Groovy truth.) cleanup: A cleanup block may only be followed by a where block, and may not be repeated. Like a cleanup method, it is used to free any resources used by a feature method, and is run even if (a previous part of) the feature method has produced an exception. As a consequence, a cleanup block must be coded defensively; in the worst case, it must gracefully handle the situation where the first statement in a feature method has thrown an exception, and all local variables still have their default values. where: A where block always comes last in a method, and may not be repeated. It is used to write data-driven feature methods Helper Methods Sometimes feature methods grow large and/or contain lots of duplicated code. In such cases it can make sense to introduce one or more helper methods. Two good candidates for helper methods are setup/cleanup logic and complex conditions. Factoring out the former is straightforward,