#testcoverage — Public Fediverse posts

🚀 Now showing test coverage directly in class diagrams.

No more guessing what's tested — it's all visual, right where you design.

#DevTools #DX #TestCoverage #CodeDesign

🚀 Now showing test coverage directly in class diagrams.

No more guessing what's tested — it's all visual, right where you design.

#DevTools #DX #TestCoverage #CodeDesign

My goal this week is to add at least 80% code coverage with unit tests for one fo my personally written apps. #developer #testcoverage

@preusslerberlin on fire at DevFest 🔥

#DevFest #DevFestBerlin #TestCoverage

C++ code coverage reports often omit function templates that are not instantiated, which can give a misleading picture of coverage. I've been trying to improve my tooling in this regard, and so added a feature to Doxide to export line data directly from source code that can be mixed in with gcov coverage data. Here's the story so far.

https://indii.org/blog/cplusplus-code-coverage-with-gcov-gcovr-doxide/

#softwaretesting #testcoverage #codecoverage #cplusplus #cpp

One semi decent programming use case I have found for LLMs is starting out unit tests to backfill coverage for an already existing untested function.

#dev #testcoverage

Opinions on #unittesting are endless: test fixtures, test factories; test doubles, mocks, and stubs. The real problem is mistaking exhaustive #testcoverage for a sensible testing strategy. They aren't synonymous.

Testing core #RubyLang methods or coupling tests for a menu bar to DB calls both miss the point. The Pareto principle is to validate *your* logic, not whether Ruby or Rails work.

Tests that can't explain app-specific features or debug non-builtin code is *muda* waste. Just don't.

@sourcenouveau if there is a gap in testing it should be easy to find, and possibly easy to fix, and I’d rather do that than write my own clone from scratch! #TestCoverage #StableSoftware

#Development #Introductions
Four common types of code coverage · What code coverage in tests is and how to measure it https://ilo.im/1551j7

_____
#WebDev #Testing #TestAutomation #SourceCode #CodeCoverage #TestCoverage #Metrics

What is an example of an open source system with an exceptionally good test suite?

The example I gave today is #SQLite, with 100% branch coverage, MC/DC testing and 600 (!) test lines per line of code.

- How SQLite is tested: https://www.sqlite.org/testing.html
- MC/DC for SQLite: https://corecursive.com/066-sqlite-with-richard-hipp/#testing-and-aviation-standards
- SQLite architecture: https://www.vldb.org/pvldb/vol15/p3535-gaffney.pdf

#sqlite #mcdc #testcoverage

#TestCoverage. 100% is too little. 80% is enough.

My proof case is literally any language divide by 0.

#python case
def inverse(x):
return 1 / x

I’ve been scouring for an example of any “mainstream” programming language that handles this without putting the burden on the dev to remember, “Oh yeah! I need to write error handling for that.”

I just wrote a #test which didn't improve my code's #TestCoverage but was absolutely vital, and which many people don't bother with. I'm writing code to generate a report. I've got copious tests that make sure the reports contain all the correct info. I added a test that they don't include wrong info. Test that your code does what you want, but also test that it doesn't do what you don't want. #NegativeTesting can find very nasty bugs.

I just wrote a #test which didn't improve my code's #TestCoverage but was absolutely vital, and which many people don't bother with. I'm writing code to generate a report. I've got copious tests that make sure the reports contain all the correct info. I added a test that they don't include wrong info. Test that your code does what you want, but also test that it doesn't do what you don't want. #NegativeTesting can find very nasty bugs.

I just wrote a #test which didn't improve my code's #TestCoverage but was absolutely vital, and which many people don't bother with. I'm writing code to generate a report. I've got copious tests that make sure the reports contain all the correct info. I added a test that they don't include wrong info. Test that your code does what you want, but also test that it doesn't do what you don't want. #NegativeTesting can find very nasty bugs.

I just wrote a #test which didn't improve my code's #TestCoverage but was absolutely vital, and which many people don't bother with. I'm writing code to generate a report. I've got copious tests that make sure the reports contain all the correct info. I added a test that they don't include wrong info. Test that your code does what you want, but also test that it doesn't do what you don't want. #NegativeTesting can find very nasty bugs.

I just wrote a #test which didn't improve my code's #TestCoverage but was absolutely vital, and which many people don't bother with. I'm writing code to generate a report. I've got copious tests that make sure the reports contain all the correct info. I added a test that they don't include wrong info. Test that your code does what you want, but also test that it doesn't do what you don't want. #NegativeTesting can find very nasty bugs.

The quality of tests tells more about the project than the #testcoverage.

forget #linecoverage use #mutationtestcoverage in #java and #kotlin with @_pitest - a short intro - #tdd #testcoverage #devsecops #innovation #java https://youtu.be/6Vej7YEOF8g

Everyone wants to add tools to the dev env, but nobody wants to support their team when they break the precommit hooks. #eslint #typescript #jest #tdd #danger #testCoverage #linting #husky

mutation testing is one of the best testcoverages in #java and #kotlin with @_pitest - a short intro - #tdd #testcoverage #devsecops #innovation #jfrog https://youtu.be/6Vej7YEOF8g

mutation testing in #java and #kotlin with @[email protected] - a short intro - #tdd #testcoverage #devsecops #innovation #jfrog https://youtu.be/6Vej7YEOF8g

forget #linecoverage use #mutationtestcoverage in #java and #kotlin with @[email protected] - a short intro - #tdd #testcoverage #devsecops #innovation #jfrog https://youtu.be/6Vej7YEOF8g