Suggestion - Add testkit tool

[hepiyellow]

The testkit tool can generate testkit (drivers) for testing.

A testkit can be devided into 2 parts: selectors, actions.

Selectors

The selectors can be easily defined in the meta data file.
For example using data-hook values.
something like:

const name = 'textContent`
const selector = `[data-hook="text-content"]`;
compMetadata.addElementSelector({name, selector});

This metadata should be independent of any testing framework (dom, protractor, puppeteer)

Actions

We can have metadata for common actions: focus, click, hover

The metadata should include the element selectors which should accept an action.
For example:

const name = 'closeButton`
const selector = `[data-hook="close-button"]`;
const actions: = [  focusable, clickable];
]
popoverMetadata.addElement({name, selector, focusable: true, actions});

Then we can generate a driver with a method:

const driver = {
  clickCloseButton()
  focusCloseButton()
}

This actions part is not refined yet, just an idea.

[JoMarton]

@hepiyellow the metadata file contains general info about the component and possible simulations (combination of props and state).

It isn't a unit or "interaction" tesging replacement, at least not currently.

If you want to simulate some actions, you can probably achieve that with a combination of state & props without defining interaction.

[hepiyellow]

I said, we would generate a driver.
I didn't say we would run interaction tests.