Something About jUnit

SPRINT3R Siam Chamnankit Co., Ltd., Odd-e (Thailand) Co., Ltd. and Alliance 1


http://less.works/less/technical-excellence/unit-testing.html


SPRINT3R Siam Chamnankit Co., Ltd., Odd-e (Thailand) Co., Ltd. and Alliance

Why not write Unit test ?

4



5

Testing for QA Time = Cost

Integration testing find more bugs

Manual testing find more bugs

Write more code


Waste time ?

6


Waste time ?

7


Why Unit test ?

8


Anatomy JUnit 4Test Name

Test Case NameAnnotation

9


Test Naming

10


“What ’s in a name ?”

That which we call a rose

by any other name would smell

Romeo and Juliet

as sweet

11


Don’t say “test”, say “should”

Guide to Test Writing

12


Don’t use the word “test”

13


Use the word “should”

14


Don’t test your class, test behaviour


15


Test class names are important too

Structure your test well


16

Tests are deliverable too


Test Structure

17


The ratio of time spent (code)

versus writing is

over 10 to 1

Robert C. Martin, Clean Code

18


Good Unit Test

Arrange

Act

Assert

19


Setup Pattern

20


Setup Pattern

Inline Setup

21


Setup Pattern

Delegate Setup

22


Setup Pattern

Implicit Setup

23


Implicit Teardown

24


Ignore Testcase

25


Handle Exception

26


Traditional approach

27


Expected Annotation

28


ExpectedException Rule

29


Data-Driven with JUnit

30

@Parameterized


Set of test data

Using parameterized

31

Expected resultDefine test that uses the test dataVerify result against expected result


Data-Driven Development

32


@Parameterized with Calculate Grade

Demo

33

Input Expected Result

80 A

70 B

60 C

50 D

40 F


Step 1 :: Test Data

34

Input Expected Result

80 A

70 B

60 C

50 D

40 F


Step 2 :: Add Runner

35


Step 3 :: Matching fields

36


Step 4 :: Define test case

37


Step 5 :: Add @parameters

38


Step 6 :: Test Result

39



40

Technology

Something About jUnit