testing - Unit or integration test resource file directory layout -
what common approaches unit or integration test resource directory's nested layout? example, if code, tests, resources strucured in java project
main/ java/ com/ example/ class.java test/ java/ com/ example/ classtest.java resources/
what approachs storing resource files test?
in extremely simple case store file e.g. test/resources/a.xml
, when have multiple tests each test has source , expected output files, doesn't work. example of solution be
test/ resources/ com/ example/ classtest/ src/ a.xml b.xml exp/ a.xml b.xml
are there common approaches structuring multiple resource files multiple tests.
honestly there many ways of doing things there developers. realistically, think abou next developer - or else 6 months or 2 years now. able understand relationships between files , code. able add new tests, maintain old, etc. conventions help?
whichever layout choose should reflect consideration because if next developer you, it's have off loaded know else. when come don't want going - "wtf thinking?" :-) want start working on again.
Comments
Post a Comment