abatar1 / simplefluenttester Goto Github PK

Sometimes, it causes printed messages to be cut off in the console. Probably, NLog or something similar should be used to avoid that.

Unit tests should be generated on project compilation that references `SimpleFluentTester package.

After the research, I've decided to use MSBuild Task feature

The choise of test framework is not finished yet, however it's not really necessary, generated test cases itself should be very simple.

As I see it, this feature should be a report configuration property.

Currently, user could override ILogger in reporter configuration with his own instance that also prints logs to files, but it adds an additional complexity of usage. The easiest way to do it may be adding file provider to a logger if this property has been set.

Also, file template and file path should be customizable as well.

I would also consider refactoring reporter configuration in a fluent way to stick to one design approach. That means that configuration should be refactored to a method chain approach, as well as this new API.

Inputs property of TestCase is object?[], but should be of type IComparedObject as well as Output and Expected properties. The goal is to avoid using nulls in a logic.