@jaimequiceno1945
.Net Consultant, BackEnd and FrontEnd Developer Analyst
I am motivated Software and Telecommunications Engineer with 9 years of experience in analysis, design, implementation, testing and deployment of software solutions.
I am passionate about knowing the context of the problem in detail to end an adequate solution applying SOLID principles and design patterns to deliver software products with quality and efficiency.
I have supported and innovated with automation various business and industrial processes through several programming languages and work frameworks with and without Agile methodologies.
I have skills and knowledge in both FrontEnd and BackEnd.
I am available to teach about design patterns applied in real life, unit testing, analysis and software development with SOLID principles.
Apr 23, 2023 · 9 min read · Creating tests We have created in part 4 of this series of posts, the implementation of the tests that cover both the happy path and the wrong path of the constructor method of our MetadataService class. Now we are going to know the implementation of...
Join discussion
Apr 23, 2023 · 3 min read · Creating tests Happy path test in the constructor method Now with our fixture service created with the builder design pattern included inside and also the GetSut method that returns the instance of the service to test, we can begin to perform our tes...
Join discussion
Apr 23, 2023 · 3 min read · Let's start with fixture service implementation Implementing IDisposible Our fixture service will be called multiple times during the execution of the tests by the ClassFixture. It is the most important service in our implementation as it will commun...
Join discussion
Apr 23, 2023 · 3 min read · Best Practices Regions Within test classes and generally, in all classes, I have always liked to divide sections or responsibilities into regions. So you will probably see some of the following most of the time: Attributes: for writing read-only pro...
Join discussion
Apr 23, 2023 · 3 min read · Intro Hello everyone. This is the first part of a series of posts that will explain a methodology that allows implementation tests in an organized way, with separate responsibilities and using most of the available resources that XUnit tests have. I ...
Join discussion