I think a unit test should only test one thing. 

It's easier to get what's wrong when it fails and unit tests are also a good source for  documentation. The more detailed they are the better the doc.

On April 20, 2014 3:26:59 AM CEST, Marko Vuksanovic <notifications@github.com> wrote:
>> @@ -0,0 +1,15 @@
>> +library map_spec;
>> +
>> +import '../_specs.dart';
>> +import 'package:angular/formatter/module.dart';
>> +
>> +void main() {
>> +  describe('map', () {
>> +    it('should convert a map to list of key value pairs',
>inject((Parser parse, FormatterMap formatters) {
>> +      List result = parse('{"key1": "value1", "key2": "value2"} |
>map').eval(null, formatters);
>> +      expect(result.map((kv) => kv.key)).toEqual( ["key1", "key2"]);
>> +      expect(result.map((kv) => kv.value)).toEqual( ["value1",
>"value2"]);
>> +      expect(parse('null | map').eval(null,
>formatters)).toEqual(null);
>
>I don't think it really matters. None of the expectations should fail
>anyways
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/angular/angular.dart/pull/931/files#r11796475