component-testing

Clone the example app, only use Mocha instead of Jest

Before picking this issue, it's recommended to have a short tech planning chat here and only then upon sync to get up to speed.

If a component has a child content parameter that is a RenderFragment<TValue>, then the parameter builder's AddChildContent method should throw an exception with an error message telling the user to use .Add(p => p.ChildContent, ...) instead.

For example, the following should throw an helpful exception:

var cut = RenderComponent<Virtualize<string>>(ps => ps
	.Add(p => p.Items, Te

Describe the bug
Most expect methods print the request and response when the assertion fails.
However, the custom expect handler does not show these objects.

To Reproduce
Steps to reproduce the behavior:

const spec = pactum.spec();
spec.get(url);
await spec.toss();
await spec.response().to.have._((ctx) => {
  assert.fail('error');
});

*Expected behavior