Overhaul project naming

My proposal:

Points to note:

• What we are currently calling ‘specs’ I tend to refer to as ‘acceptance tests’. I.e. black box tests written in the language of the public API which ignore all implementation details
• What we are currently calling ‘integration tests’ are what I tend to refer to as ‘component tests’. I.e. semi-white box testing of subsets of the implementation details behind the public API
• Unit test remain as the name for white box testing of individual classes which may or may not form part of the public API
• On disk, all test projects will be moved to a ‘tests’ subfolder of ‘Source’ (or ‘src’ if we agree on #279)
• The framework suffix is mandatory on all projects to avoid ambiguity and the suffixes used match the nuget framework identifiers but using .NET casing rules
• ‘FakeItEasy.IntegrationTests.External’ is removed and the formatter it contains is moved to ‘FakeItEasy.Examples.Net40’. If we choose to implement #281 then we will need to do something else. Perhaps we can keep the project and just rename it to ‘FakeItEasy.Tests.Component.External.Net40’.
• The rake tasks spec and integ would be renamed to accept and component

Looking forward to hearing any opinions on this.

[thomaslevesque]

👍 to close

[adamralph]

I’m not sure if this issue is still valid. We only have one version of each project now. Shall we close this?

I’m still not so happy with the naming of our test projects, but I can spin off a separate issue for that if it bothers me enough.