Problem with having a single unit test

[vieiralucas]

Currently unit tests for get-func-name are so tiny and simple that I can just copy and paste it over here 😄

'use strict';
var assert = require('simple-assert');
var getFuncName = require('..');
describe('getFuncName', function () {
  it('getFuncName', function () {
    // Asserting that `getFuncName` behaves correctly
    function /*one*/correctName/*two*/() { // eslint-disable-line no-inline-comments, spaced-comment
      return 0;
    }
    function withoutComments() {
      return 1;
    }

    var anonymousFunc = (function () {
      return function () { // eslint-disable-line func-style
        return 2;
      };
    }());
    assert(getFuncName(correctName) === 'correctName');
    assert(getFuncName(withoutComments) === 'withoutComments');
    assert(getFuncName(anonymousFunc) === '');
  });
});

I know this is beautiful, but...

• If the test fails, we wont be able to tell what's going on just by reading the message.
  
  What have I broke here? Imagine if this fails only in IE running over saucelabs 😸.
• If this keeps growing I'm afraid that this can become very confusing like the utilities tests of chaijs/chai.

As @meeber suggested here, I think that we should refactor this test and split it so it has a single assertion per test and better names.
I understand that get-func-name should not grow a lot and will probably stay very simple, but I don't see this as a good reason to not have good descriptive tests.

If you guys agree. I'll be very happy to make a PR addressing this.

[lucasfcosta]

I totally agree.
That would be great.