I have a project where many challenges are to ensure that the software supports flat text files Works correctly with
I found that it does not make sense to enjoy the input from flat files because the main thing to solve is to actually work with those special files.
Example If the output output changes in the external system then the unit must fail in the test.
The unit-testing of code written with files gives very little sense and creates very little business value (as the compress code will take a very long time to empower and reality will produce one hundred and one line methods. ).
Just want to repeat - challenge software is able to work with successful files, keep a strict tab and TDD is to make it verification at any time.
What will be the suggestion? How can it be systematic, defined, implemented?
Is there any specification for the format of flat files?
If this is the case, then you should include sample files, which have each specifications of the specification, and write a test for each feature.
If flat files are not in accordance with any specification, you can not actually do TDD on them - it can always contain a new file which is unknown. In this case you have to write about it in your own specification (based on observation / research) and TDD. But you will still be open for anonymous data breaking your code.
Moral? Make sure you have at least one work practice specification.
Comments
Post a Comment