Build new API

[kkozmic]

We pretty much agreed that making conventions standard test methods is the only way to get proper tooling support (and it has its advantages as well).

As such we need a new API that will be as simple to use and readable as the old one (or better), will be extensible to support pre-baked conventions, customisations etc, and will be nicely usable inside test methods.

Given most of the test frameworks these days work through a static entry point type (see Assert in testing frameworks, Substitute, A in mocking frameworks etc I think we should explore similar style of API, as discussed in comments for #8

[JakeGinnivan]

Where is this at?

What else needs to be done? :P

[kkozmic]

a whole bunch of stuff :)

I have a semi-done change related to .csproj based conventions that operates at a higher level of abstraction than XDocument

We also could use a bunch of higher level API for specifying how to find the types we want to use for the type based conventions (so that we hide Reflection/Cecil API

I think I'm going to take that and put it in my current project and see what scenarios I find that the API is missing or inadequate.

After that we may close this one and split the outstanding work into separate issues. This one is an unspecified bag that is impossible to say when it's done done, or not :)

API is like art - never finished, only abandoned :)

[JakeGinnivan]

I think this issue can be closed, the external API has stayed pretty stable for a while. We can gradually improve it, but this issue is no longer actionable