Well usually, the update action returns 204. But there are some cases in which it returns an updated entity. I think whatever you choose you won’t make a mistake. But if your requirement is for the PUT action to return only the status code if it is successful, then just leave it with 204.

Thank you for your valuable time. I tried to implement put using following code.

// Arrange
            ILogger<ProductCategoryController> logger = GetLogger();
            var _unitOfWork = MockIUnitOfWork.GetMock();
            var productcategoryController = new ProductCategoryController(_unitOfWork.Object, logger);
            var productCategory = new ProductCategory()
            {
                ProductCategoryId=1,
                CategoryName = "Skin Care"
            };
            // Act
            var result = await productcategoryController.UpdateProductCategory(1, productCategory) as ObjectResult;
            // Assert
            Assert.NotNull(result);
            Assert.Equal(StatusCodes.Status204NoContent, result!.StatusCode);

But it is returning null. The update and delete methods just return a status code while the create method returns the added entity. Should I modify these two methods as well like the create method?
Lets say if it works after updating. The question is, should I really update it to make it work as we usually return NoContent(204) on update or delete.

 [HttpPut("{id}")]
        public async Task<IActionResult> UpdateProductCategory(int id, [FromBody] ProductCategory productCategory)
        {
            try
            {
                if (id != productCategory.ProductCategoryId)
                    return NotFound();


                if (ModelState.IsValid)
                {
                    if (!_unitOfWork.ProductCategoryRepo.ProductCategoryExists(productCategory.ProductCategoryId))
                        return NotFound();


                    _unitOfWork.ProductCategoryRepo.Update(productCategory);
                    await _unitOfWork.SaveAsync();
                    return NoContent();
                }
                return BadRequest();
            }
            catch (Exception ex)
            {
                string error = ErrorBuilder.BuildErrorMessage(ex);
                _logger.LogError(MyLogEvents.UpdateItem, error);
                return StatusCode(StatusCodes.Status500InternalServerError);
            }
        }

🙂 Well yeah. Maybe someone can find my answer inappropriate like I don’t want to spend time to reply the reader, but it is not like that. The best way to learn something is to try it by yourself, find the issue and fix it. Knowledge gained that way stays much longer in our heads 🙂

Thanks, Now I know the reason 🙂

To be honest, the best way to answer that is to use this example without mocking those two and inspect the result.

Hello Pedro. To be honest, I didn’t try it, but maybe this can help: https://code-maze.com/csharp-mock-asynchronous-methods-using-moq/. If only being async is an issue, I think this should be a solution. Again, I really didn’t try it, just wanted to mention it.