This document summarizes unit testing done for core methods using the NUnit testing framework integrated with Jenkins. It discusses the testing framework used, naming conventions for test cases, the Arrange Act Assert pattern for writing test cases, sample test cases, goals of unit testing, and concludes with a demonstration and Q&A. A total of 496 test cases were written to test 6 core methods.

1. Bordas Shop
Unit Tests
27th October 2013

2. Objective
Automated test
Test for core methods only
Integrated with Jenkins
Build success only if all test success
Total 496 test cases for 6 core methods

3. Testing Framework – NUnit
Version 2.6
Written entirely in C#
Many advantages of .NET.
E.g. custom attributes and reflection.
Jenkins NUnit Plugin for build automation
NUnit = xUnit of .NET languages
Free

4. Change of plan
Visual
Studio
Unit
Testing
Framework
NUnit

5. Naming
Roy osherov
Author of “Art of unit testing”
blog “Naming standards for unit tests”
[UnitOfWork_StateUnderTest_ExpectedBehavior]
GetProducts_Availability_NotNullExpected
GetProducts_CheckPriceLessThanOrEqualZero_CountZeroExp
ected
GetStreet_CheckDuplicateId_InputPostCode1113_CountZeroEx
pected

6. A A A
Arrange: setup everything needed.
Act: Invoke the code under test.
Assert: Specify the pass criteria for the
test, which fails it if not met.
In 2003 William C. Wake blogged about
using Arrange Act Assert pattern in unit
tests.

7. A A A
Arrange, Act, Assert

8. Sample test case 1
Check by different combination

9. Sample test case 2
Don’t miss boundary values

10. Sample test case 3
Make sure exception is thrown where is should

11. NUnit

12. Jenkins

13. Goals
Glitch free methods
Tested methods
Fully functional methods
Tension free modification
A form of documentation.
Confidence

14. Demonstration

15. Q & A

16. Thank you