TIBCOSoftware / flogo

Project Flogo is an open source ecosystem of opinionated event-driven capabilities to simplify building efficient & modern serverless functions, microservices & edge apps.
http://flogo.io
BSD 3-Clause "New" or "Revised" License
2.41k stars 288 forks source link

Ability to test flow from CLI #290

Open vijaynalawade opened 6 years ago

vijaynalawade commented 6 years ago

I'm submitting a ... (check one with "x")

[] bug report => search github for a similar issue or PR before submitting
[x] feature request
[] support request
[] general question

Current behavior (how does the issue manifest): Like Web UI where developers can quickly test their flows, developers should be able automate their flow testing through CLI.

Expected behavior: ./<BINARY> --test -flow <FLOW_NAME> -input <FLOW_INPUT_PARAM_JSON> ./<BINARY> --test -flow <FLOW_NAME> -inputfile <FLOW_INPUT_PARAM_JSON_FILE> e.g. ./MyApp --test -flow MyFlow -input '{"p1": "test", "p2": 20}' ./MyApp --test -flow MyFlow -inputfile ~/test/myapp_myflow_input.json Minimal steps to reproduce the problem (not required if feature enhancement):

What is the motivation / use case for changing the behavior? Developer productivity and automation Please tell us about your environment (Operating system, docker version, browser & web ui version, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X 0.5.4 Additional information you deem important (e.g. issue happens only occasionally):

mellistibco commented 4 years ago

@skothari-tibco this could make a nice cli plugin...

skothari-tibco commented 4 years ago

Yes. Looks neat.