It seems problematic to allow arbitary non-lowercase attribute on HTML nodes. Because the server has no ability to keep them case sensitive (HTML isn't). So they will end up different on the client.

We should probably warn if the attribute is not a known one *and* is not lowercase.
expect(e.getAttribute('stroke-dasharray')).toBe('10 10');
        },
      );
    });
    describe('unknown attributes', function() {
      itRenders('unknown attributes', async render => {
        const e = await render(<div foo="bar" />);
        expect(e.getAttribute('foo')).toBe('bar');
      });
      itRenders('unknown data- attributes', async render => {
        const e = await render(<div data-foo="bar" />);
        expect(e.getAttribute('data-foo')).toBe('bar');
      });
      itRenders('badly cased reserved attributes', async render => {
        const e = await render(<div CHILDREN="5" />, 1);
        expect(e.getAttribute('CHILDREN')).toBe('5');
      });
      itRenders('"data" attribute', async render => {
        
        const e = await render(<object data="hello" />);
        expect(e.getAttribute('data')).toBe('hello');
      });
      itRenders('no unknown data- attributes with null value', async render => {
        const e = await render(<div data-foo={null} />);
        expect(e.hasAttribute('data-foo')).toBe(false);
      });
      itRenders('unknown data- attributes with casing', async render => {
        const e = await render(<div data-fooBar="true" />);
        expect(e.getAttribute('data-fooBar')).toBe('true');
      });