how classify c++ exam apps associated files?


i'm operative c++ library (among stuff) functions review config files; i wish supplement tests this. far, lead me emanate lots current unfair config files, any wholly few lines exam specific functionality. nonetheless got unequivocally unwieldy, there files, also lots little c++ exam apps. somehow seems wrong me :-) have hints classify tests, exam apps, exam data?



note: library's open api itself simply testable (it requires config record parameter). juicy, bug-prone methods indeed reading interpreting config values private, i don't proceed exam directly?



so: hang contrast opposing genuine files; so, classify files apps still maintainable?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?