CODE Magazine / Articles

Testing

Articles filed under Testing

Articles

Showing 1–11 of 11

  1. CODE Magazine: 2023 - May/Jun cover

    Using Moq: A Simple Guide to Mocking for .NET

    Moq is a mocking library for C# .NET that can help developers achieve better unit testing by improving the isolation of tests. This article explains how to use Moq for mocking, including its features such as parameter matching, setups, verification, and sequences. Moq's fluent interface is easy to use compared to other mocking libraries and it enforces loosely coupled software design using dependency injection, resulting in modular code that is easier to test, read, and extend. The article concludes with additional resources for further reading on Moq.

  2. CODE Magazine: 2023 - January/February cover

    An Introduction to Distributed Tracing with OpenTelemetry in .NET 7

    OpenTelemetry is an open-source distributed tracing framework. Companies that use it can make more informed decisions about their operations. Learn to use it through an example ASP.NET 7 project.

  3. CODE Magazine: 2021 - July/August cover

    Test Your REST APIs Using Insomnia REST Client

    APIs are everywhere! Joydip shows you how to take advantage of them using a new, free, cross-platform desktop framework, Insomnia, with its user-friendly interface and sophisticated features.

  4. CODE Magazine: 2019 - January/February cover

    A Professional-Grade Configuration for Azure DevOps Services: Beyond the Quickstarts

    Jeffrey shows you how to organize your code to suit DevOps, configure the five Azure DevOps products, automate your pipeline for speed, and build quality into each stage of your process.

  5. CODE Magazine: 2019 - January/February cover

    Part 3: Merrily We Roll Along

    Rod continues the tale of an enormous conversion project.

  6. CODE Magazine: 2017 - November/December cover

    Software Archaeology

    In "Software Archaeology," Chris Williams explores the challenges and strategies of working with legacy code, drawing from his extensive experience as a developer since the 1980s. The article delves into practical approaches for understanding and maintaining old or unfamiliar codebases, such as mapping functionality, leveraging debugging tools, and resisting the urge to refactor unnecessarily. Through real-world examples, including his own projects and inherited applications, Chris emphasizes the importance of balancing practicality with respect for existing architectural choices, while offering actionable tips to navigate the complexities of outdated systems. Ultimately, he advocates for adaptability and structured exploration to tame the chaos of legacy software.

  7. CODE Magazine: 2017 - September/October cover

    Improving Code Quality with Unit Tests

    Insufficient testing can lead to devastating results. Find out what you can do to minimize outages as Keith explores unit testing using a Python tool called Coverage.py.

  8. CODE Magazine: 2017 - July/August cover

    Beta Test Your iOS Applications Using TestFlight

    Jason explores TestFlight, a new tool for testing your iOS apps. It has some nifty notification tools, which make it easier to have a lot of testers—or just a few, depending on what your product needs. Check out what else it has going for it.

  9. CODE Magazine: 2017 - May/June cover

    What’s New in Visual Studio 2017

    It’s so new that the dust is still settling, and VS2017 was worth the wait. Markus explores the ins and outs of his favorite new features.

  10. CODE Magazine: 2017 - March/April cover

    Data-Driven Testing with Visual Studio

    Does the idea of using an app that’s never been tested give you the willies? It should, and Paul talks about finding the sticking points so you can be confident that your code works as intended before someone fires it up.

  11. CODE Magazine: 2013 - July/August cover

    Asynchronous, Test-Driven Development, with JavaScript and Mocha

    Although I’m now a huge advocate of test-driven-development, I was not an immediate convert to the school of thought. I understood the necessity of unit testing: