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
Flowtrace can be captured of issues found in production. Want to be able to go quickly to a reproducable test-case - to understand, fix and ensure issue does not happen again.
A tool could allow specifying a flowtrace, and an an fbp-spec file (with already existing topic/fixture/testcases). It would read the test topic, then go through the trace to find the inputs/output to that component. Then create a testcase with this input and skeleton/empty expectations, and modify the YAML file to include the new testcase.
Tool would be used (primarily) manually by developers. But one can imagine automated uses, where a production failure would automatically create testcase, put it through CI against newest/development version of the software.
The text was updated successfully, but these errors were encountered:
Flowtrace can be captured of issues found in production. Want to be able to go quickly to a reproducable test-case - to understand, fix and ensure issue does not happen again.
A tool could allow specifying a flowtrace, and an an fbp-spec file (with already existing topic/fixture/testcases). It would read the test
topic
, then go through the trace to find the inputs/output to that component. Then create a testcase with this input and skeleton/empty expectations, and modify the YAML file to include the new testcase.Tool would be used (primarily) manually by developers. But one can imagine automated uses, where a production failure would automatically create testcase, put it through CI against newest/development version of the software.
The text was updated successfully, but these errors were encountered: