it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

Today I was checking out the library and MSVC warns for https://github.com/alandefreitas/matplotplusplus/blob/359a775710e1b1fd5667281a0855806f149b7ab0/source/matplot/util/contourc.cpp#L1771

BOUNDARY_S returns a bool do the expression is bool > 0

Description

Currently our unit tests are disorganized and each test creates example StellarGraph graphs in different or similar ways with no sharing of this code.

This issue is to improve the unit tests by making functions to create example graphs available to all unit tests by, for example, making them pytest fixtures at the top level of the tests (see https://docs.pytest.org/en/latest/

For different use cases, like bencheeorg/benchee_html#10 it'd be great to have statistics about statistics - what I'd call "meta statistics" - although there's probably some better real statistics name for this :)

What should be in there (that I know of so far):

• job size (how many jobs are in there)
• minimum of run times over all jobs
• maximum of run times over all jobs

This should be

Describe the bug
On the link component textAnchor is used as a style property like so: <text style={{ textAnchor: "middle" }} {...textProps}> but textProps contains style and thus overwrites the style property for textAnchor.

https://github.com/danielcaldas/react-d3-graph/blob/0ac8c470c3d6c7e20bf1faf761d449fa753a1b88/src/components/link/Link.jsx#L96-L103

Here style gets o