You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A potential way to structure this, is to create a test.rkt file in the same directory as the subgraph/agent.
The test.rkt file should contain a quickcheck property definition, these definitions and the graphs to be tested against should all be packaged up and sent to the fvm for processing.
The test harness should be able to handle testing of a single node only for development purposes.
Property based checks should be run by the CI upon every commit.
A rackunit exception should be thrown if a property fails.
The text was updated successfully, but these errors were encountered:
clacke
added a commit
to clacke/fractalide
that referenced
this issue
Jul 10, 2018
This collection no longer exists.
Solution: Load fractalide/nodes/rkt/paging-jsend-get/main instead.
`raco test .` in the root of fractalide successfully runs the test.
This should be in `release.nix` and more modules should have tests in
their `test` submodule. But first we should make running node tests
more convenient, which I guess goes under fractalide#238. Once we have that,
quicktest is just one way to formulate a test case.
The way paging-jsend-get tests itself can be viewed as a first
prototype and an example of what kind of boilerplate we would
like to put into a convenience interface.
Instead of being an external module, test/mock could be a submodule --
if we think spreading files around doesn't look nice and if the mock
is small enough. It's possible that we could make a mock generator
macro that creates a mock for your needs as a submodule, to keep the
mock definition concise.
Solution:
A potential way to structure this, is to create a
test.rkt
file in the same directory as the subgraph/agent.The
test.rkt
file should contain a quickcheck property definition, these definitions and the graphs to be tested against should all be packaged up and sent to the fvm for processing.The test harness should be able to handle testing of a single node only for development purposes.
Property based checks should be run by the CI upon every commit.
A
rackunit
exception should be thrown if a property fails.The text was updated successfully, but these errors were encountered: