Rethink table test utils.

[jodator]

As @Reinmar pointed-out: ckeditor/ckeditor5-table#127 (comment).

The table tests might not be easy to read because of use modelTable() helpers (as I think).

Those methods were created to quickly write table (layout) tests so instead of writing:

setData( model,
	'<table>' +
		'<tableRow>' +
			'<tableCell><paragraph>00[]</paragraph></tableCell>' +
			'<tableCell><paragraph>01</paragraph></tableCell>' +
		'</tableRow>' +
		'<tableRow>' +
			'<tableCell><paragraph>10</paragraph></tableCell>' +
			'<tableCell><paragraph>11</paragraph></tableCell>' +
		'</tableRow>' +
	'</table>'
);

The helper creates proper structure:

setData( model, modelTable( [
	[ '00[]', '01' ],
	[ '10', '11' ]
] ) );

Note: similar helper is created for the view which properly stub table string with all widget markup.

This helper can create also proper <thead>/<tobdy> section (for the view), add arbitrary attributes to the table cell. And will also create a table with other children then <paragraph> if they are provided as content.

While it is easier to write them other devs have to learn them to know what happens in some cases.

My question is: do we have some other ideas for the above?

[jodator]

Closing in favour of the recent one #6574. This issue is outdated and the tests needs to be updated as the feature grow.

We also introduce a tool by @niegowski that allows to create better comments in tests when needed.