[WIP] Update status document with test coverage information

[itaiferber]

This brings Docs/Status.md up to date with the current state of implementation as part of an effort to improve documentation and test coverage across the project. With up-to-date information, it will be easier to see what components of our project require additional work, and more importantly, where we can improve in testing.

This PR is not ready to merge as I will be pushing additional commits showing the actual state of test coverage, but I wanted to get this up in case anyone had comments or concerns with this initiative. I also intend to update our contribution guidelines to highlight that, ideally, PRs and changes to our codebase should also come with update to sections in the corresponding tables to reflect coverage and completeness.

(I recommend viewing the document to see what the proposed table format looks like.)

[parkera]

Looks great!

[itaiferber]

@parkera Thanks. :)
I originally had an additional column in each table for what file every entity was defined in (for easy lookup, and to note that, say, NSDateInterval is actually defined in NSDate.swift), but the tables are already pretty wide... Not sure if that's information we care to preserve, but it's an option.

In any case, I'll be updating this over the course of the next day or so so we hopefully get a better idea of where we're really lacking.

[iainsmith]

This sentence left me a bit confused. I was wondering if you meant one of the following?

Methods which do not require a concrete implementation remain unimplemented

or

Methods which do not require a concrete implementation need updating to reflect this.

[itaiferber]

Good eye, thanks for catching this. I'd meant the first one — all methods which are not implemented in terms of NSRequiresConcreteImplementation() have been left NSUnimplemented(), and need implementations. I will push a correction.

[itaiferber]

@parkera When you get the chance, can you please review the changes I've added to our guidelines? I want to make sure the public-facing text is appropriate

[itaiferber]

@parkera @phausler @michael-lehew Also, if you guys wouldn't mind sanity-checking the latest revision, I would appreciate it

I want to make sure that everything seems reasonable before merging

[parkera]

LGTM