![\"PUZZLE-1-min\"](\"\/wp-content\/uploads\/2016\/05\/PUZZLE-1-min.png\")
<\/a><\/p>\nUnit test yazarken kolay mock i\u015flemlerimizi yapabilmemizi sa\u011flayan\u00a0NSubstitute Framework<\/strong>‘\u00fcnden bahsedece\u011fim bu yaz\u0131mda. Bu framework’den bahsetmeden \u00f6nce k\u0131saca Mock <\/strong>nedir ve\u00a0neden ihtiya\u00e7 duyar\u0131z’\u0131 bir hat\u0131rlamam\u0131zda fayda olaca\u011f\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcyorum.<\/p>\n Mock kavram\u0131 istedi\u011fimiz bir objenin yerine ge\u00e7ebilen fake objelerdir<\/strong>.\u00a0Bu objelerin istedi\u011fimiz gibi davranmalar\u0131n\u0131 sa\u011flayabiliriz.<\/p><\/blockquote>\n K\u0131saca Mock\u00a0kavram\u0131ndan bahsetti\u011fimize g\u00f6re art\u0131k yava\u015f\u00e7a kodlamaya ba\u015flayabiliriz. Haydi bakal\u0131m! :)<\/p>\n Not:\u00a0NSubstitute framework’\u00fc open-source’dur. Buradan <\/a>ilgili repository’sine ula\u015fabilirsiniz.<\/p><\/blockquote>\n \u00d6ncelikle Test Case’lerimizi yazabilmek i\u00e7in bir Unit Test<\/strong> projesi olu\u015ftural\u0131m. Olu\u015fturmu\u015f oldu\u011fumuz bu projeye “Nuget Package Manager” \u00fczerinden “NSubstitute” yazarak,\u00a0a\u015fa\u011f\u0131 g\u00f6rseldeki\u00a0framework’\u00fc kural\u0131m.<\/p>\n Gerekli kurulumu yapt\u0131ktan sonra test i\u015flemleri i\u00e7in basit bir senaryo haz\u0131rlayal\u0131m. Varsayal\u0131m ki bir e-ticaret sitesi geli\u015ftiriyoruz ve \u00fcr\u00fcn stok i\u015flemlerini yapabilmemiz i\u00e7in bir servisimiz bulunmakta. Bizim i\u00e7in kritik olan bu servis i\u00e7in ilgili business logic’inin bozulmad\u0131\u011f\u0131n\u0131 do\u011frulayabilmek ad\u0131na Unit Test yazmak istiyoruz. Bu senaryomuzu uyarlamak ad\u0131na basit bir \u015fekilde Test Driven Development<\/strong>‘a uygun olarak haz\u0131rlayal\u0131m.<\/p>\n Not: Test i\u015flemlerimizi tam anlam\u0131yla ger\u00e7ekleyebilmemiz i\u00e7in kesinlikle projelerimizin Test Driven Development’a ve SOLID prensiplerine uygun bir \u015fekilde geli\u015ftirilmi\u015f olup, abstraction’lar\u0131n do\u011fru uygulanmas\u0131\u00a0gerekmektedir.<\/p><\/blockquote>\n NSubstitute Framework’\u00fc ile kolayl\u0131kla Mock olu\u015fturabilmek i\u00e7in a\u015fa\u011f\u0131daki syntax’\u0131 kullanmam\u0131z yeterlidir.<\/p>\n Bu i\u015flem sonucunda ilgili T tipimiz i\u00e7in bir Mock i\u015flemini ba\u015flataca\u011f\u0131m\u0131z\u0131 s\u00f6yl\u00fcyoruz ve ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 inject ediyoruz. Daha sonras\u0131nda ise\u00a0bu ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n hangi method i\u00e7in nas\u0131l davranmas\u0131 gerekti\u011fini, unit test senaryolar\u0131m\u0131z do\u011frultusunda a\u015fa\u011f\u0131daki syntax ile kolayl\u0131kla belirleyebiliyoruz.<\/p>\n Burada mockObject’in “T” tipinden “Sum” method’unun int tipinde iki parametre alaca\u011f\u0131n\u0131 belirtiyoruz. Dilersek de bu iki parametre sonucunda yapmas\u0131 gereken davran\u0131\u015f\u0131 da s\u00f6yleyebiliriz!<\/p>\n “Sum” method’unun i\u015flem sonucunda ise “Returns” extension’\u0131 ile geriye “10” de\u011ferini d\u00f6nmesi gerekti\u011fini s\u00f6yl\u00fcyoruz. \u0130\u015fte hepsi bu kadar.<\/p>\n \u015eimdi \u00f6rnek\u00a0projemiz i\u00e7in \u00f6ncelikle entity’leri tan\u0131mlayal\u0131m:<\/p>\n Product<\/strong> entity’si basit bir \u015fekilde senaryo gere\u011fi sadece Id, Name ve Stock property’lerine sahip olacakt\u0131r.<\/p>\n \u015eimdi contract’lar\u0131m\u0131z niteli\u011finde olan interface’lerimizi tan\u0131mlayal\u0131m:<\/p>\n IProductRepotistory<\/strong> Product i\u015flemlerimizi ger\u00e7ekle\u015ftirmemizi sa\u011flayan repository contract’\u0131m\u0131z niteli\u011findedir ve i\u00e7erisinde sadece “GetById” method’unu bar\u0131nd\u0131rmaktad\u0131r.<\/p>\n IStockRepository<\/strong> ise,\u00a0ilgili stock i\u015flemlerini farkl\u0131 bir tabloda ger\u00e7ekle\u015ftirecek olan repository contract’\u0131m\u0131zd\u0131r. “ChangeStock” method’u ile stock i\u015flemlerini ger\u00e7ekle\u015ftirecektir.<\/p>\n ILogger<\/strong> ise, olmazsa olmaz\u0131m\u0131zd\u0131r. Her bir exception’u\u00a0“Log” method’u ile bir yerlerde kaydetmekteyiz. :)<\/p>\n \u015eimdi geldik \u015fu me\u015fhur \u00fcr\u00fcn stok i\u015flemlerini ger\u00e7ekle\u015ftirecek olan servisi tan\u0131mlamaya.<\/p>\n ProductStockService<\/strong> class’\u0131 ise basit bir \u015fekilde\u00a0constructor arac\u0131l\u0131\u011f\u0131 ile inject etti\u011fi ba\u011f\u0131ml\u0131l\u0131klar\u0131<\/strong> kullanarak, “ChangeStock” method’u ile ilgili stock i\u015flemlerini ger\u00e7ekle\u015ftirmektedir.<\/p>\n Dikkat ederseniz Mock’un faydalar\u0131n\u0131 hat\u0131rlarken\u00a0bahsetmi\u015f oldu\u011fumuz; “Unit test bir birimi test etti\u011fi i\u00e7in, oradaki ak\u0131\u015f\u0131 test ederken bu ak\u0131\u015fa ba\u011fl\u0131 olan dependency\u2018lerin test ak\u0131\u015f\u0131n\u0131 bozmamas\u0131n\u0131 sa\u011flar.” k\u0131sm\u0131na bir kez daha dikkat \u00e7ekmek isterim. Bizim bu servis \u00fczerindeki yapmak istedi\u011fimiz i\u015flem “ChangeStock” method’unun ilgili stok de\u011fi\u015ftirme business logic’inin d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131d\u0131r asl\u0131nda. Bizi ne o an “_productRepository” \u00fczerinden \u00fcr\u00fcn\u00fcn gelip gelmedi\u011fi ilgilendiriyor, nede “_stockRepository” i\u00e7erisindeki i\u015flem. \u0130\u015fte tam burada Mock objeler imdad\u0131m\u0131za ko\u015fuyor! Ger\u00e7ekte yoklar, ama asl\u0131nda varlar gibi. :) Buradaki amac\u0131m\u0131z i\u015fin \u00f6z\u00fcnde bu d\u0131\u015f ba\u011f\u0131ml\u0131l\u0131klar\u0131m\u0131zdan kurtularak, as\u0131l hedefimiz d\u00fczg\u00fcn \u00e7al\u0131\u015fabilmesidir.<\/p>\n Haydi \u015fimdi\u00a0mock’layarak,\u00a0test senaryolar\u0131m\u0131z\u0131 olu\u015ftural\u0131m.<\/p>\n ProductStockServiceTests\u00a0class’\u0131 \u00e7at\u0131s\u0131na bakt\u0131\u011f\u0131m\u0131zda, klasik olarak t\u00fcm testlerimiz “Initialize” ile ba\u015flay\u0131p, “Cleanup” method’u ile son buluyor. \u00a0Test yazma logic’imizde ise yine\u00a0standartlar do\u011frultusunda gidebilmek i\u00e7in\u00a0AAA (Arrange, Act, Assert) pattern’ini uyguluyoruz. Detayl\u0131 bilgi i\u00e7in buradan<\/a>\u00a0ula\u015fabilirsiniz. \u015eimdi gelelim bakal\u0131m neler yapt\u0131k?<\/p>\n T\u00fcm interface’lerimizi global olarak tan\u0131mlayarak, “Initialize” method’u i\u00e7erisinde bahsetmi\u015f oldu\u011fumuz:<\/p>\n syntax’\u0131n\u0131 kullanarak, framework’e T tipindeki interface’lerimiz i\u00e7in mock i\u015flemini ger\u00e7ekle\u015ftirece\u011fimizi\u00a0belirttik.\u00a0Daha sonra “ChangeStock_WhenProductNotNull_Change” isminde bir \u00f6rnek senaryo olu\u015fturduk. Bu senaryo gere\u011fi stok de\u011fi\u015ftirme i\u015fleminin, product objesinin null gelmedi\u011fi durumlarda de\u011fi\u015fmesini beklemekteyiz. Bunun i\u00e7in method’un “Arrange” k\u0131sm\u0131nda,\u00a0ProductStockService<\/strong> class’\u0131n\u0131n “ChangeStock” i\u015flevini yerine getirebilmesi i\u00e7in ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 bulundu\u011fu “ProductRepository” ve “StockRepository” i\u00e7in senaryonun ba\u015far\u0131l\u0131 olup, business logic’i test edebilmemiz ad\u0131na, istedi\u011fimiz do\u011frultuda mock objeler olu\u015fturduk. Bunun i\u00e7in:<\/p>\n syntax’\u0131 ile,\u00a0T tipinin int olaca\u011f\u0131n\u0131 ve 10’dan k\u00fc\u00e7\u00fck olaca\u011f\u0131n\u0131 belirttik. Bu i\u015flemin sonucunda ise, test senaryomuzun ba\u015far\u0131l\u0131 \u00e7al\u0131\u015fabilmesi ad\u0131na, geriye fake\u00a0bir Product<\/strong>\u00a0objesi\u00a0d\u00f6nmesi gerekti\u011fini s\u00f6yledik. \u0130kinci sat\u0131r\u0131nda ise, bu i\u015flemler sonucunda “StockRepository” i\u00e7erisindeki “ChangeStock” method’ununda:<\/p>\n parametreleri ile Product ve int tipinde herhangi bir objenin gelebilece\u011fi\u00a0belirttik. Bunun sonucunda ise senaryomuz gere\u011fi ba\u015far\u0131l\u0131 bir sonu\u00e7 bekledi\u011fimiz i\u00e7in “true” de\u011ferini d\u00f6nmesini gerekti\u011fini s\u00f6yledik. Act k\u0131sm\u0131na bakt\u0131\u011f\u0131m\u0131zda ise art\u0131k ProductStockService<\/strong> class’\u0131 \u00fczerinde “ChangeStock” method’unu,\u00a0productId’si “5” ve stock de\u011feri ise “50” olarak \u00e7a\u011f\u0131rd\u0131k.<\/p>\n Bu i\u015flemler sonucunda mock objelerimiz devreye girece\u011fi\u00a0i\u00e7in ilgili servis s\u0131n\u0131f\u0131 i\u00e7erisindeki business logic ba\u015far\u0131l\u0131 \u00e7al\u0131\u015facakt\u0131r ve\u00a0Assert k\u0131sm\u0131 true de\u011ferini alarak test senaryomuz\u00a0ba\u015far\u0131yla ger\u00e7ekle\u015fmi\u015f\u00a0olacakt\u0131r.<\/p>\n Bir di\u011fer senaryomuz olan “ChangeStock_WhenProductNull_WriteLogMessage” method’una bakt\u0131\u011f\u0131m\u0131zda ise, Product objesinin null oldu\u011fu durumlarda, ba\u015far\u0131l\u0131 bir \u015fekilde log at\u0131p atamat\u0131\u011f\u0131m\u0131za bakmaktay\u0131z. Hi\u00e7 bir mock objesi kullanmad\u0131\u011f\u0131m\u0131z i\u00e7in ilgili servis \u00e7a\u011fr\u0131s\u0131 yap\u0131ld\u0131\u011f\u0131nda Product objesi null olaca\u011f\u0131 i\u00e7in “_logger.Log()” method’u devreye girecektir. Assert k\u0131sm\u0131nda ise yine\u00a0NSubstitute Framework’\u00fcn\u00fcn bize sa\u011flam\u0131\u015f oldu\u011fu “Received” extension’u ile, “_logger” class’\u0131 i\u00e7erisindeki “Log” method’unun herhangi bir string parametresi ile \u00e7a\u011fr\u0131l\u0131p \u00e7a\u011fr\u0131lmad\u0131\u011f\u0131n\u0131 kontrol ettirmekteyiz.<\/p>\n Bunun gibi bir \u00e7ok kolayl\u0131k sunan bu extension’lara bakmak isterseniz e\u011fer, buradan <\/a>ula\u015fabilirsiniz.<\/p>\n B\u00f6ylelikle bir makalemin daha sonuna geldik. Bir sonraki makalelerimde g\u00f6r\u00fc\u015fmek\u00a0dile\u011fiyle.\u00a0 \u00d6rnek olarak ger\u00e7ekle\u015ftirmi\u015f oldu\u011fumuz projeye ekten ula\u015fabilirsiniz.<\/p>\nMock\/Mocklamak Nedir?<\/h4>\n
Mock\/Mocklamak Bize Ne Sa\u011flar?<\/h4>\n
\n
<\/a><\/p>\nNSubstitute ile Mock Olu\u015fturma<\/h4>\n
var mockObject = Substitute.For<T>();<\/pre>\n
var mockObject = Substitute.For<T>();\r\n\r\nmockObject.Sum(Arg.Any<int>(),Arg.Any<int>());<\/pre>\n
var mockObject = Substitute.For<T>();\r\n\r\nmockObject.Sum(Arg.Any<int>(),Arg.Any<int>())\r\n.Returns(10);<\/pre>\n
\u00d6rnek Bir Unit Test Senaryosu ve Mock \u0130\u015flemi<\/h4>\n
namespace UnitTestMockingSample\r\n{\r\n public class Product\r\n {\r\n public int Id { get; set; }\r\n public string Name { get; set; }\r\n public int Stock { get; set; }\r\n }\r\n}<\/pre>\nnamespace UnitTestMockingSample\r\n{\r\n public interface IProductRepository\r\n {\r\n Product GetById(int productId);\r\n }\r\n}<\/pre>\nnamespace UnitTestMockingSample\r\n{\r\n public interface IStockRepository\r\n {\r\n bool ChangeStock(Product product, int stock);\r\n }\r\n}<\/pre>\nnamespace UnitTestMockingSample\r\n{\r\n public interface ILogger\r\n {\r\n void Log(string message);\r\n }\r\n}<\/pre>\nusing System;\r\n\r\nnamespace UnitTestMockingSample.Business\r\n{\r\n public class ProductStockService\r\n {\r\n private readonly IProductRepository _productRepository;\r\n private readonly IStockRepository _stockRepository;\r\n private readonly ILogger _logger;\r\n\r\n public ProductStockService(IProductRepository productRepository, IStockRepository stockRepository, ILogger logger)\r\n {\r\n _productRepository = productRepository;\r\n _stockRepository = stockRepository;\r\n _logger = logger;\r\n }\r\n\r\n public bool ChangeStock(int productId, int stock)\r\n {\r\n Product product;\r\n\r\n try\r\n {\r\n product = _productRepository.GetById(productId);\r\n }\r\n catch (Exception ex)\r\n {\r\n _logger.Log(ex.ToString());\r\n\r\n return false;\r\n }\r\n\r\n if (product != null)\r\n {\r\n \/\/ bla bla stock i\u015flem business logic'leri...\r\n\r\n return _stockRepository.ChangeStock(product, stock);\r\n }\r\n else\r\n {\r\n _logger.Log(\"Stok bilgisi de\u011fi\u015ftirilemedi.\");\r\n\r\n return false;\r\n }\r\n }\r\n }\r\n}\r\n<\/pre>\n<\/h4>\n
using Microsoft.VisualStudio.TestTools.UnitTesting;\r\nusing NSubstitute;\r\nusing UnitTestMockingSample.Business;\r\n\r\nnamespace UnitTestMockingSample\r\n{\r\n [TestClass]\r\n public class ProductStockServiceTests\r\n {\r\n private IProductRepository _productRepository;\r\n private IStockRepository _stockRepository;\r\n private ILogger _logger;\r\n\r\n private ProductStockService _productStockService;\r\n\r\n [TestInitialize]\r\n public void Initialize()\r\n {\r\n _productRepository = Substitute.For<IProductRepository>();\r\n _stockRepository = Substitute.For<IStockRepository>();\r\n _logger = Substitute.For<ILogger>();\r\n\r\n _productStockService = new ProductStockService(_productRepository, _stockRepository, _logger);\r\n }\r\n\r\n [TestMethod]\r\n public void ChangeStock_WhenProductNotNull_Change()\r\n {\r\n \/\/ Arrange\r\n _productRepository.GetById(Arg.Is<int>(a => a < 10))\r\n .Returns(new Product() { Name = \"Asus PDA\", Stock = 100});\r\n\r\n _stockRepository.ChangeStock(Arg.Any<Product>(), Arg.Any<int>())\r\n .Returns(true);\r\n\r\n \/\/ Act\r\n var result = _productStockService.ChangeStock(5, 50);\r\n\r\n \/\/ Assert\r\n Assert.IsTrue(result);\r\n }\r\n\r\n [TestMethod]\r\n public void ChangeStock_WhenProductNull_WriteLogMessage()\r\n {\r\n \/\/ Act\r\n _productStockService.ChangeStock(5, 50);\r\n\r\n \/\/ Assert\r\n _logger.Received().Log(Arg.Any<string>());\r\n }\r\n\r\n [TestCleanup]\r\n public void Cleanup()\r\n {\r\n _productRepository = null;\r\n _stockRepository = null;\r\n _logger = null;\r\n }\r\n }\r\n}<\/pre>\nSubstitute.For<T>();<\/pre>\n
Arg.Is<T>(expression)<\/pre>\n
Arg.Any<Product>(), Arg.Any<int>()<\/pre>\n