Organizing and namespacing tests.

It’s been a long-time beef of mine that tests are written as giant, single files with all constants globally namespaced and no descriptors for tests generally. What do people think of adopting a convention in lieu of a proper TDD framework to better organize tests? Something like…

// #add
{
  // it should accept numbers
  {
    const a: number = add(1 + 1)
  }
  
  // it should error when we pass null
  {
    // $ExpectError
    const a: number = add(1 + null)
  }
}

And so on. Thoughts? If we did adopt any convention, it’d be important that it could be incrementally adopted.

[villesau]

I’ve been wrapping my tests in functions, something like here: https://github.com/flowtype/flow-typed/blob/master/definitions/npm/angular_v1.5.x/flow_v0.47.x-/test_angular_scope_v1.5.x.js

[AndrewSouthpaw]

Well, I fixed the library so now we can use describe and it blocks as first-class functions, just like in an ordinary testing environment. #1928 for more info. Here’s to better testing! 🥂