To solve the problem stated in the z-input issue maybe nightmare is a good option.
Switching to nightmare should end the selenium problems and speed the testing process and It would have the same end result as nightwatch considering each z-kit component is only testing regression against Chrome for the moment and nightmare's engine (electron) is very similar.
Testing compatibility with other browsers is crucial but can be postponed to a z-kit page containing all the components and then tests could be applied to make sure the z-kit suite is compatible with most currently used browsers.
To solve the problem stated in the z-input issue maybe nightmare is a good option.
Switching to nightmare should end the selenium problems and speed the testing process and It would have the same end result as nightwatch considering each z-kit component is only testing regression against Chrome for the moment and nightmare's engine (electron) is very similar.
Testing compatibility with other browsers is crucial but can be postponed to a z-kit page containing all the components and then tests could be applied to make sure the z-kit suite is compatible with most currently used browsers.