We need to write an article similar to https://github.com/hdorgeval/testcafe-snippets/blob/master/say-goodbye-to-flakyness.md. There should be a list of best practices that help writing stable and reusable tests.

This area of the readme needs some rework, W3C spec is now conformant on most browsers and we should be recommending people use selenium - Just point them to the drivers and use proper browsers. https://github.com/cucumber/godog#testing-browser-interactions

I know a few people said they wanted to help maintain, this would be a good first issue.

Hello,

It should be nice to have the list of different endpoints available and the different parameters so we could call Cerberus API's easily. (https://swagger.io/)

many methods are missing, any eta on the implementation?

I was interested in addnode for example

thanks

In order to extend tomato functionality, it would be nice to have a concrete example of how to write a custom resource.

Currently, EAT using Actor(http://docs.paralleluniverse.co/quasar).
But it doesn't provide external communication. So it has limitation to extends.
To have load test, we can run it with multi-JVM.

But. expand to centralized-management(which can command to agents and monitor it) function, Actor model of EAT should have new Actor model(which can communicate with external nodes).

Currently I'

When you run the example test from the Readme you expect one test to run. But instead there are two tests running. Same test runs twice.
Let me know if I need to provide more info!

Currently, the passing tests simply show up in a simple list. A flag (e.g. --verbose) should be provided so that each expected item within the passing test can be inspected. Examples where this is useful:

• test passes under multiple conditions that are discernible from the assertions
• report information can be further used (part of the response, the result of test fixtures, etc)