10 article(s) tagged “Dev Tools”. ← All Posts
Making CTest save its results to files with outputLogFile and outputJUnitFile in a CMake test preset: a plain text log for humans and a JUnit XML report for CI tools, from one cmake --workflow command.
Read More →Adding gcov code coverage to a C project with CMake --coverage, running gcov as a CTest test with fixtures, and reading the .gcov report to find the lines my Unity tests never touched.
Read More →Writing my first real C unit tests with ThrowTheSwitch Unity, fetching it automatically with CMake FetchContent, and running them with CTest using one cmake --workflow --preset test command.
Read More →Using CMakePresets.json and an add_custom_target run target so one cmake --workflow command configures, builds and runs a C project: configure, build and workflow presets explained for beginners.
Read More →Reviewing AI-generated C99 math code (arithmetic, power/abs/clamp, statistics) like a tester before writing CTest tests: header files, include guards, pure functions, and the edge cases that become the test plan.
Read More →
A no-fluff cheat sheet of the five Claude Code slash commands I use every day: what each does, why I use it, and how to run it.
Read More →Learn how to build a reusable Tkinter dialog with cancel handling you can drop into any Python data or analysis project in minutes.
Read More →A practical SDET's guide to using AI for PR reviews, test generation, and repetitive tasks — without losing your craft.
Read More →
Set up Claude Code the right way on existing Python projects — from virtual envs to /init — so you get actually useful AI help from the start.
Read More →Before you write a single line of Tkinter code, here's how to decide whether a desktop app — or a humble spreadsheet — is actually the right tool for your team.
Read More →