Download as PPSX, PPTX
![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](https://image.slidesharecdn.com/c850d767-5058-4f1b-b072-119ea32f0f71-151230205044/75/Unit-Test-Presentation-5-2048.jpg)
Uploaded bySayedur Rahman
Unit Test Presentation
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.
In this document
Powered by AI
Presentation on Bordas Shop Unit Tests dated 27th October 2013.
Focus on automated testing with 496 test cases for 6 core methods integrated with Jenkins.
Introduction to NUnit 2.6, advantages of .NET and Jenkins NUnit Plugin for automation.
Transitioning to Visual Studio's Unit Testing Framework with NUnit.
Naming standards by Roy Osherov for unit tests emphasizing clarity in test names.
Outline of the AAA pattern for unit testing, introduced by William C. Wake in 2003.
Reiterating the Arrange, Act, Assert pattern essential for structuring unit tests.
Sample test case showcasing the importance of testing combinations.
Highlighting the significance of boundary value analysis in test case design.
Stress on ensuring exceptions are thrown appropriately in unit tests.
Reinforcing the choice of NUnit for conducting unit tests.
Emphasis on Jenkins as a tool for build automation in testing processes.
Objectives include glitch-free, documented, and confidently modified methods.
Demonstration segment to showcase the unit testing process.
Q&A segment to clarify doubts regarding unit testing.
Closure of the presentation with gratitude expressed to the audience.
![[기본과정] 코드 테스트와 커버리지 기본 교육(개념)](https://cdn.slidesharecdn.com/ss_thumbnails/basicofcodeleveltestandcoverage-190203041600-thumbnail.jpg?width=640&height=640&fit=bounds)
![[오픈소스컨설팅] 쿠버네티스와 쿠버네티스 on 오픈스택 비교 및 구축 방법](https://cdn.slidesharecdn.com/ss_thumbnails/osck8svsk8sonopenstackkhoj-210310051504-thumbnail.jpg?width=640&height=640&fit=bounds)
![Selenium 4 with Simon Stewart [Webinar]](https://cdn.slidesharecdn.com/ss_thumbnails/selenium4browserstackwebinar-190702161824-thumbnail.jpg?width=640&height=640&fit=bounds)
Unit Test Presentation
- 1. Bordas Shop Unit Tests 27thOctober 2013
- 2. Objective Automated test Test forcore 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.
- 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 case1 Check by different combination
- 9. Sample test case2 Don’t miss boundary values
- 10. Sample test case3 Make sure exception is thrown where is should
- 11.
- 12.
- 13. Goals Glitch free methods Testedmethods Fully functional methods Tension free modification A form of documentation. Confidence
- 14.
- 15.
- 16.